From: Yinan Liu <yinan@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mark-pk.tsai@mediatek.com, peterz@infradead.org,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] scripts: ftrace - move the nop-processing in ftrace_init to compile time
Date: Sat, 11 Sep 2021 23:28:32 +0800 [thread overview]
Message-ID: <de1bbbc9-3d66-a3dd-550f-509032be20ba@linux.alibaba.com> (raw)
In-Reply-To: <20210911101247.4a37ec51@rorschach.local.home>
This is my GCC version: GCC version 4.8.5 20150623 (red hat 4.8.5-44)
(GCC) .
In fact, I see the make_nop processing in recordmcount. I'm still
confused why this part can be directly replaced?
在 2021/9/11 下午10:12, Steven Rostedt 写道:
> On Sat, 11 Sep 2021 21:50:43 +0800
> Yinan Liu <yinan@linux.alibaba.com> wrote:
>
>> When ftrace is enabled, ftrace_init will consume a period of
>> time, usually around 15~20ms. Approximately 60% of the time is
>> consumed by nop-processing. Moving the nop-processing to the
>> compile time can speed up the kernel boot process.
>>
>> performance test:
>> env: Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz
>> method: before and after patching, compare the
>> total time of ftrace_init(), and verify
>> the functionality of ftrace.
>>
>> avg_time of ftrace_init:
>> with patch: 7.114ms
>> without patch: 15.763ms
> What compiler are you using? Because by default, gcc should already do
> this for you. In fact, recordmcount isn't even called with the latest
> gcc, as gcc creates mcount_loc and inserts nops.
>
> This was implemented before, but because we use to have "ideal nops"
> that was determined at run time, because the different CPUs had
> different efficiency on what nop was used, we had to do it at run time.
> But that is no longer the case today, so we can revisit this.
>
>> Signed-off-by: Yinan Liu <yinan@linux.alibaba.com>
>> ---
>> kernel/trace/ftrace.c | 4 ++++
>> scripts/recordmcount.h | 14 ++++++++++++++
>> 2 files changed, 18 insertions(+)
>>
>> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
>> index c236da868990..ae3fba331179 100644
>> --- a/kernel/trace/ftrace.c
>> +++ b/kernel/trace/ftrace.c
>> @@ -6261,6 +6261,10 @@ static int ftrace_process_locs(struct module *mod,
>> * until we are finished with it, and there's no
>> * reason to cause large interrupt latencies while we do it.
>> */
>> +#if defined CONFIG_X86 || defined CONFIG_X86_64 || defined CONFIG_ARM || defined CONFIG_ARM64
> We don't list archs in generic files. The above needs to be something like:
>
> #ifdef ARCH_HAS_MCOUNT_NOP
>
> or some name like that, and then that macro gets defined by the arch
> header (include/asm/ftrace.h)
>
>
>
>> + ret = 0;
>> + goto out;
>> +#endif
> space should be here.
>
>> if (!mod)
>> local_irq_save(flags);
>> ftrace_update_code(mod, start_pg);
> -- Steve
next prev parent reply other threads:[~2021-09-11 15:28 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 13:50 [PATCH 0/2] ftrace: improve ftrace during compiling Yinan Liu
2021-09-11 13:50 ` [PATCH 1/2] scripts: ftrace - move the sort-processing in ftrace_init to compile time Yinan Liu
2021-09-11 13:59 ` Steven Rostedt
2021-10-03 13:42 ` Yinan Liu
2021-10-08 23:48 ` Steven Rostedt
2021-10-09 2:56 ` Yinan Liu
2021-10-25 13:20 ` Yinan Liu
2021-10-25 15:00 ` Steven Rostedt
2021-09-11 13:50 ` [PATCH 2/2] scripts: ftrace - move the nop-processing " Yinan Liu
2021-09-11 14:12 ` Steven Rostedt
2021-09-11 15:28 ` Yinan Liu [this message]
2021-09-11 16:07 ` Peter Zijlstra
2021-09-11 14:33 ` Peter Zijlstra
2021-09-11 17:15 ` kernel test robot
2021-09-11 18:04 ` kernel test robot
2021-11-16 2:49 ` [PATCH v2 0/2] ftrace optimization at " Yinan Liu
2021-11-16 2:49 ` [PATCH v2 1/2] scripts: ftrace - move the sort-processing in ftrace_init to " Yinan Liu
2021-11-16 8:07 ` Peter Zijlstra
2021-11-16 12:42 ` Yinan Liu
2021-11-16 13:05 ` Peter Zijlstra
2021-11-16 14:46 ` Yinan Liu
2021-11-17 13:34 ` kernel test robot
2021-11-16 2:49 ` [PATCH v2 2/2] scripts: ftrace - move the nop-processing " Yinan Liu
2021-11-16 8:10 ` Peter Zijlstra
2021-11-16 12:51 ` Yinan Liu
2021-11-16 13:07 ` Steven Rostedt
2021-11-16 15:02 ` Yinan Liu
2021-11-16 16:06 ` Steven Rostedt
2021-11-22 13:43 ` [PATCH v3] scripts: ftrace - move the sort-processing " Yinan Liu
2021-11-23 10:54 ` [PATCH v4] ftrace sorting optimization changelog Yinan Liu
2021-11-23 10:54 ` [PATCH v4] scripts: ftrace - move the sort-processing in ftrace_init to compile time Yinan Liu
2021-11-29 2:13 ` Yinan Liu
2021-11-29 3:51 ` Steven Rostedt
2021-11-29 6:52 ` Yinan Liu
2021-11-30 17:08 ` Steven Rostedt
2021-12-01 5:32 ` [PATCH v5 0/2] ftrace sorting optimization changelog Yinan Liu
2021-12-01 5:32 ` [PATCH v5 1/2] scripts: ftrace - move the sort-processing in ftrace_init to compile time Yinan Liu
2021-12-01 21:45 ` Steven Rostedt
2021-12-05 12:35 ` [scripts] 12955fb1c5: kernel-selftests.livepatch.test-ftrace.sh.fail kernel test robot
2021-12-01 5:32 ` [PATCH v5 2/2] script/sorttable: code style improvements Yinan Liu
2021-12-02 2:16 ` [PATCH v6 0/2] ftrace sorting optimization changelog Yinan Liu
2021-12-02 2:16 ` [PATCH v6 1/2] scripts: ftrace - move the sort-processing in ftrace_init Yinan Liu
2021-12-02 17:58 ` Steven Rostedt
2021-12-05 12:45 ` Masami Hiramatsu
2021-12-06 20:18 ` Steven Rostedt
2021-12-07 1:29 ` Yinan Liu
2021-12-02 2:16 ` [PATCH v6 2/2] script/sorttable: code style improvements Yinan Liu
2021-12-02 15:30 ` [PATCH v6 0/2] ftrace sorting optimization changelog Peter Zijlstra
2021-12-07 15:13 ` [PATCH v7 0/2] ftrace sorting optimization Yinan Liu
2021-12-07 15:13 ` [PATCH v7 1/2] scripts: ftrace - move the sort-processing in ftrace_init Yinan Liu
2021-12-11 14:50 ` Steven Rostedt
2021-12-07 15:13 ` [PATCH v7 2/2] script/sorttable: code style improvements Yinan Liu
2021-12-12 11:33 ` [PATCH v8 0/1] change log Yinan Liu
2021-12-12 11:33 ` [PATCH v8] scripts: ftrace - move the sort-processing in ftrace_init Yinan Liu
2022-01-21 9:46 ` Sven Schnelle
2022-01-21 10:42 ` Heiko Carstens
2022-01-21 11:14 ` Sven Schnelle
2022-01-21 11:29 ` Sven Schnelle
2022-01-21 18:11 ` Steven Rostedt
2022-01-22 9:17 ` Heiko Carstens
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=de1bbbc9-3d66-a3dd-550f-509032be20ba@linux.alibaba.com \
--to=yinan@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
Powered by JetHome