From: Chengming Zhou <zhouchengming@bytedance.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, catalin.marinas@arm.com, will@kernel.org,
mark.rutland@arm.com, broonie@kernel.org,
songmuchun@bytedance.com, qirui.001@bytedance.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH] arm64/ftrace: Make function graph use ftrace directly
Date: Wed, 23 Feb 2022 16:00:27 +0800 [thread overview]
Message-ID: <5d64733b-8d2a-4928-c4dc-ce4f3b5fc561@bytedance.com> (raw)
In-Reply-To: <20220222105218.28e3d5aa@gandalf.local.home>
On 2022/2/22 11:52 下午, Steven Rostedt wrote:
> On Tue, 22 Feb 2022 21:00:49 +0800
> Chengming Zhou <zhouchengming@bytedance.com> wrote:
>
>> As we do in commit 0c0593b45c9b ("x86/ftrace: Make function graph
>> use ftrace directly"), we don't need special hook for graph tracer,
>> but instead we use graph_ops:func function to install return_hooker.
>>
>> Since commit 3b23e4991fb6 ("arm64: implement ftrace with regs") add
>> implementation for FTRACE_WITH_REGS on arm64, we can easily adopt
>> the same optimization on arm64.
>
> Note. Ideally we want it to hook with DYNAMIC_FTARCE_WITH_ARGS, and not
> FTRACE_WITH_REGS. If arm64 is like x86_64, saving all regs at every
> function call has a bit more overhead than saving the minimum. The
> DYNAMIC_FTRACE_WITH_ARGS, means that the minimum is still saved, but now
> exposes the arguments and the stack pointer, which function_graph_tracer
> needs.
Yes, it would be better to implement DYNAMIC_FTRACE_WITH_ARGS on arm64 too,
and this patch just use DYNAMIC_FTRACE_WITH_REGS to install return_hooker
for graph tracer, so it's a code cleanup, no performance optimization.
Thanks.
>
> -- Steve
>
>
>>
>> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
>> ---
next prev parent reply other threads:[~2022-02-23 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:00 Chengming Zhou
2022-02-22 15:52 ` Steven Rostedt
2022-02-22 16:07 ` Mark Rutland
2022-02-23 8:00 ` Chengming Zhou [this message]
2022-02-24 1:30 ` [External] " Steven Rostedt
2022-02-24 2:03 ` Chengming Zhou
2022-02-22 15:54 ` Mark Rutland
2022-02-22 16:05 ` Steven Rostedt
2022-02-23 7:55 ` [External] " Chengming Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d64733b-8d2a-4928-c4dc-ce4f3b5fc561@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=qirui.001@bytedance.com \
--cc=rostedt@goodmis.org \
--cc=songmuchun@bytedance.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®