From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Primiano Tucci <primiano@google.com>
Subject: [PATCH v2 0/2] tracing/probes: Add 'symstr' type for probes
Date: Thu, 27 Oct 2022 00:48:19 +0900 [thread overview]
Message-ID: <166679929981.1528100.11309260111368557859.stgit@devnote3> (raw)
Hi,
Here is the 2nd version of the patches to add the 'symstr' type for
kprobe/eprobe events.
This version removes redundant strlen()[1/2] and fixes indentation
[2/2].
This type converts given value into kernel symbol string and stores
it as a dymanic symbol in the trace ring buffer entry. Thus, user who
reads the raw ring buffer data doesn't need to resolve the symbol
name afterwards.
This is similar to the existing 'symbol' type. The 'symbol' type
stores the address value itself to the entry, it only *shows* the
symbol name when it is printed.
Thank you,
---
Masami Hiramatsu (Google) (2):
tracing/probes: Add symstr type for dynamic events
tracing/probes: Reject symbol/symstr type for uprobe
Documentation/trace/kprobetrace.rst | 8 ++
kernel/trace/trace.c | 2 -
kernel/trace/trace_probe.c | 65 +++++++++++++-------
kernel/trace/trace_probe.h | 19 ++++--
kernel/trace/trace_probe_tmpl.h | 47 ++++++++++++++
kernel/trace/trace_uprobe.c | 3 +
.../ftrace/test.d/kprobe/uprobe_syntax_errors.tc | 5 ++
7 files changed, 113 insertions(+), 36 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2022-10-26 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 15:48 Masami Hiramatsu (Google) [this message]
2022-10-26 15:48 ` [PATCH v2 1/2] tracing/probes: Add symstr type for dynamic events Masami Hiramatsu (Google)
2022-10-26 15:48 ` [PATCH v2 2/2] tracing/probes: Reject symbol/symstr type for uprobe Masami Hiramatsu (Google)
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=166679929981.1528100.11309260111368557859.stgit@devnote3 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=primiano@google.com \
--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