From: "yebin (H)" <yebin10@huawei.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: <rostedt@goodmis.org>, <mathieu.desnoyers@efficios.com>,
<linux-trace-kernel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] support '%pd' and '%pD' for print file name
Date: Sat, 20 Jan 2024 14:26:39 +0800 [thread overview]
Message-ID: <65AB679F.9070402@huawei.com> (raw)
In-Reply-To: <20240119234356.1598e760edbfa58f5440a941@kernel.org>
On 2024/1/19 22:43, Masami Hiramatsu (Google) wrote:
> On Fri, 19 Jan 2024 09:38:45 +0800
> Ye Bin <yebin10@huawei.com> wrote:
>
>> During fault locating, the file name needs to be printed based on the
>> dentry/file address. The offset needs to be calculated each time, which
>> is troublesome. Similar to printk, kprobe supports printing file names
>> for dentry/file addresses.
> Hi Ye,
>
> Thanks for your proposal!
>
> Generically, I think this type of hack is not good for the tracing
> because there are already some ways to do that. e.g.
> - Use perf probe to specify dentry->name:string or file->name:string
> - Use BTF to specify in the same way (but only for function entry)
> And those are more obvious what it does.
>
> However, if this is implemented in more generic syntax, it will be
> acceptable.
> For example, type specifying with "arg1:printfmt(%pD)" will be
> more generic because it is apparently one of the printfmt and output
> string. Or, maybe we can just allow to use ":%pD" as a fetch type
> (start with '%' means the printfmt)
>
> Also, could you update readme_msg[] in kernel/trace/trace.c if
> you add a type, and add a testcase of selftests/ftrace, for this
> feature? Documentation should also be updated with more syntax
> information.
>
> Thank you,
Thank you very much for your suggestion.
I will re-implement this function according to your suggestion.
>> Ye Bin (3):
>> tracing/probes: support '%pd' type for print struct dentry's name
>> tracing/probes: support '%pD' type for print struct file's name
>> Documentation: tracing: add new type 'pd' and 'pD' for kprobe
>>
>> Documentation/trace/kprobetrace.rst | 3 +-
>> kernel/trace/trace_probe.c | 50 +++++++++++++++++++++++++++++
>> 2 files changed, 52 insertions(+), 1 deletion(-)
>>
>> --
>> 2.31.1
>>
>
prev parent reply other threads:[~2024-01-20 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 1:38 [PATCH 0/3] support '%pd' and '%pD' for print file name Ye Bin
2024-01-19 1:38 ` [PATCH 1/3] tracing/probes: support '%pd' type for print struct dentry's name Ye Bin
2024-01-19 14:57 ` Masami Hiramatsu
2024-01-20 0:59 ` kernel test robot
2024-01-20 6:27 ` kernel test robot
2024-01-19 1:38 ` [PATCH 2/3] tracing/probes: support '%pD' type for print struct file's name Ye Bin
2024-01-19 1:38 ` [PATCH 3/3] Documentation: tracing: add new type 'pd' and 'pD' for kprobe Ye Bin
2024-01-19 14:43 ` [PATCH 0/3] support '%pd' and '%pD' for print file name Masami Hiramatsu
2024-01-19 15:52 ` Steven Rostedt
2024-01-20 7:15 ` Masami Hiramatsu
2024-01-20 6:26 ` yebin (H) [this message]
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=65AB679F.9070402@huawei.com \
--to=yebin10@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.