From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Shijie Huang <shijie@amperemail.onmicrosoft.com>
Cc: Huang Shijie <shijie@os.amperecomputing.com>,
patches@amperecomputing.com, cl@linux.com,
yang@os.amperecomputing.com, peterz@infradead.org,
jpoimboe@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH resend ] tracepoint: Print the function symbol when tracepoint_debug is set
Date: Thu, 6 Mar 2025 11:37:27 -0500 [thread overview]
Message-ID: <0e691a3e-1406-4496-b7e4-8b1679b59b5d@efficios.com> (raw)
In-Reply-To: <20250306101315.5a5f1d7f@gandalf.local.home>
On 2025-03-06 10:13, Steven Rostedt wrote:
> On Thu, 6 Mar 2025 11:37:38 +0800
> Shijie Huang <shijie@amperemail.onmicrosoft.com> wrote:
>
>> diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
>> index abfd0ac1177f..5a5041f32cc8 100644
>> --- a/kernel/tracepoint.c
>> +++ b/kernel/tracepoint.c
>> @@ -127,7 +127,8 @@ static void debug_print_probes(struct
>> tracepoint_func *funcs)
>> return;
>>
>> for (i = 0; funcs[i].func; i++)
>> - printk(KERN_DEBUG "Probe %d : %p\n", i, funcs[i].func);
>> + printk(KERN_DEBUG "Probe %d : [ %p ] %pS\n",
>> + i, funcs[i].func, funcs[i].func);
>> }
>>
>>
>> The output will look like:
>>
>> [ 63.818829] Probe 0 : [ 0000000032848d41 ]
>> perf_trace_sched_wakeup_template+0x0/0x20
>> [ 63.819287] Probe 0 : [ 00000000fe8cca4d ]
>> perf_trace_sched_switch+0x0/0x20
>> [ 65.325638] Probe 0 : [ 0000000032848d41 ]
>> perf_trace_sched_wakeup_template+0x0/0x20
>> [ 65.695631] Probe 0 : [ 00000000fe8cca4d ]
>> perf_trace_sched_switch+0x0/0x20
>
> I'm fine either way. Mathieu, what's your preference?
>
> Although the above shows a hashed %p. Is that even useful?
The hashed %p is not really useful.
I think we could just print %Sb
e.g. from core-api/printk-formats.rst:
%pSb versatile_init+0x0/0x110 [module_name ed5019fdf5e53be37cb1ba7899292d7e143b259e]
AFAIU, when the kallsyms_lookup_buildid fails, it prints the raw address instead
(see __sprint_symbol).
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-03-06 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 1:55 Huang Shijie
2025-03-05 13:53 ` Mathieu Desnoyers
2025-03-05 15:47 ` Steven Rostedt
2025-03-06 2:26 ` Shijie Huang
2025-03-06 3:37 ` Shijie Huang
2025-03-06 15:13 ` Steven Rostedt
2025-03-06 16:37 ` Mathieu Desnoyers [this message]
2025-03-07 3:03 ` Shijie Huang
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=0e691a3e-1406-4496-b7e4-8b1679b59b5d@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=cl@linux.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shijie@amperemail.onmicrosoft.com \
--cc=shijie@os.amperecomputing.com \
--cc=yang@os.amperecomputing.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
all inboxes | Powered by JetHome®