From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Yinan Liu <yinan@linux.alibaba.com>,
peterz@infradead.org, mark-pk.tsai@mediatek.com,
mingo@redhat.com, linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v6 1/2] scripts: ftrace - move the sort-processing in ftrace_init
Date: Sun, 5 Dec 2021 21:45:32 +0900 [thread overview]
Message-ID: <20211205214532.bac420c582b0c9905d5d815e@kernel.org> (raw)
In-Reply-To: <20211202125800.7b346733@gandalf.local.home>
Hi Steve,
On Thu, 2 Dec 2021 12:58:00 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 2 Dec 2021 10:16:05 +0800
> Yinan Liu <yinan@linux.alibaba.com> wrote:
>
> > When the kernel starts, the initialization of ftrace takes
> > up a portion of the time (approximately 6~8ms) to sort mcount
> > addresses. We can save this time by moving mcount-sorting to
> > compile time.
> >
> > Signed-off-by: Yinan Liu <yinan@linux.alibaba.com>
> > Reported-by: kernel test robot <lkp@intel.com>
>
> After applying this, I get a failure on the kprobe self tests at boot up:
>
> Testing ftrace filter: OK
> trace_kprobe: Testing kprobe tracing:
> trace_kprobe: Could not probe notrace function kprobe_trace_selftest_target
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 1 at kernel/trace/trace_kprobe.c:1973 kprobe_trace_self_tests_init+0x5c/0x497
> Modules linked in:
> CPU: 2 PID: 1 Comm: swapper/0 Tainted: G W 5.16.0-rc3-test+ #40
> Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v03.03 07/14/2016
> RIP: 0010:kprobe_trace_self_tests_init+0x5c/0x497
> Code: 5f d7 94 ff 00 0f 85 48 04 00 00 48 c7 c7 c0 ff 8e 88 e8 6b bb cd fd 48 c7 c7 20 00 8f 88 e8 a9 b6 db fc 41 89 c4 85 c0 74 16 <0f> 0b 48 c7 c7 a0 00 8f 88 41 bc 01 00 00 00 e8 44 bb cd fd eb 33
> RSP: 0000:ffffc90000037d00 EFLAGS: 00010282
> RAX: 00000000ffffffea RBX: 0000000000000000 RCX: dffffc0000000000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8880c2b33eb4
> RBP: 1ffff92000006fa9 R08: ffffffff872e1900 R09: 0000000080000171
> R10: fffff52000006f15 R11: 0000000000000001 R12: 00000000ffffffea
> R13: 0000000000000007 R14: ffffffff8a608098 R15: ffffffff8a6080a0
> FS: 0000000000000000(0000) GS:ffff8880c2b00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000009260e001 CR4: 00000000001706e0
> Call Trace:
> <TASK>
> ? init_kprobe_trace+0x1c4/0x1c4
> do_one_initcall+0x89/0x2b0
> ? trace_event_raw_event_initcall_finish+0x150/0x150
> ? parameq+0x90/0x90
> ? _raw_spin_unlock_irqrestore+0x19/0x40
> kernel_init_freeable+0x35a/0x3e7
> ? console_on_rootfs+0x52/0x52
> ? _raw_spin_unlock+0x30/0x30
> ? rest_init+0xf0/0xf0
> ? rest_init+0xf0/0xf0
> kernel_init+0x19/0x140
> ret_from_fork+0x22/0x30
> </TASK>
> ---[ end trace 27c06839fac37d16 ]---
I confirmed this warning, but also I saw below warning too.
Maybe this also came from same commit?
[ 4.936720] Testing tracer function_graph: FAILED!
[ 6.186714] ------------[ cut here ]------------
[ 6.187301] WARNING: CPU: 0 PID: 1 at kernel/trace/trace.c:1953 run_tracer_selftest+0x13b/0x192
[ 6.187698] Modules linked in:
[ 6.188698] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.16.0-rc3+ #174
[ 6.189381] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/4
[ 6.189698] RIP: 0010:run_tracer_selftest+0x13b/0x192
[ 6.190698] Code: 60 48 c7 c6 00 6b 35 82 48 89 df e8 d3 18 33 00 4c 89 2d a4 82 a8 00 41 89 c4 b
[ 6.191698] RSP: 0000:ffffc90000013e48 EFLAGS: 00010246
[ 6.192250] RAX: 0000000000000007 RBX: ffffffff823ff940 RCX: ffff88807dc00000
[ 6.192697] RDX: 0000000000000000 RSI: ffffffff810c7983 RDI: ffffffff810c7983
[ 6.193697] RBP: ffffc90000013e60 R08: 0000000000000000 R09: ffffc90000013c40
[ 6.194415] R10: 0000000000000001 R11: 0000000000000001 R12: 00000000ffffffed
[ 6.194697] R13: ffffffff8241c620 R14: ffffffff8266e290 R15: 0000000000000000
[ 6.195698] FS: 0000000000000000(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000
[ 6.196698] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6.197317] CR2: 0000000000000000 CR3: 000000000220c000 CR4: 00000000000006b0
[ 6.197700] Call Trace:
[ 6.198698] <TASK>
[ 6.199017] register_tracer+0x123/0x1d4
[ 6.199698] ? init_graph_tracefs+0x2d/0x2d
[ 6.200159] init_graph_trace+0x62/0x64
[ 6.200583] do_one_initcall+0x48/0x200
[ 6.200699] kernel_init_freeable+0x1f0/0x23f
[ 6.201180] ? rest_init+0xd0/0xd0
[ 6.201699] kernel_init+0x1a/0x130
[ 6.202132] ret_from_fork+0x22/0x30
[ 6.202703] </TASK>
[ 6.203098] ---[ end trace e84e39016448db0f ]---
[ 6.203804] NET: Registered PF_NETLINK/PF_ROUTE protocol family
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-12-05 12:45 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
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 [this message]
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=20211205214532.bac420c582b0c9905d5d815e@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yinan@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).