From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: linux-trace-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
mhiramat@kernel.org, Martin KaFai Lau <martin.lau@linux.dev>,
bpf@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>
Subject: [PATCH v3 0/9] tracing: Improbe BTF support on probe events
Date: Wed, 26 Jul 2023 21:59:53 +0900 [thread overview]
Message-ID: <169037639315.607919.2613476171148037242.stgit@devnote2> (raw)
Hi,
Here is the 3rd version of series to improve the BTF support on probe events.
The previous series is here:
https://lore.kernel.org/all/168960739768.34107.15145201749042174448.stgit@devnote2/
The fixes patch in the previous version has been sent in different series.
https://lore.kernel.org/all/169024903018.395371.1006584451160707296.stgit@devnote2/
In this version, I added BTF support on module symbols (this will be the
biggest change) [1/9] and cleanup the btf APIs [2/9][3/9] according to
the comment. Also [5/9] introduce a query_btf_context() for simplifying
common fields in traceprobe_parse_context. [8/9] added more complex test
case for structure field access. And [9/9] update the documentation about
the mixture of '.' and '->'.
This series can be applied on top of "probes/core" branch of
https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git/
You can also get this series from:
git://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git topic/fprobe-event-ext
Thank you,
---
Masami Hiramatsu (Google) (9):
tracing/probes: Support BTF argument on module functions
bpf/btf: tracing: Move finding func-proto API and getting func-param API to BTF
bpf/btf: Add a function to search a member of a struct/union
tracing/probes: Support BTF based data structure field access
tracing/probes: Support BTF field access from $retval
tracing/probes: Add string type check with BTF
tracing/fprobe-event: Assume fprobe is a return event by $retval
selftests/ftrace: Add BTF fields access testcases
Documentation: tracing: Update fprobe event example with BTF field
Documentation/trace/fprobetrace.rst | 64 ++-
include/linux/btf.h | 8
kernel/bpf/btf.c | 84 +++
kernel/trace/trace_eprobe.c | 4
kernel/trace/trace_fprobe.c | 59 ++
kernel/trace/trace_kprobe.c | 1
kernel/trace/trace_probe.c | 487 +++++++++++++++-----
kernel/trace/trace_probe.h | 27 +
kernel/trace/trace_uprobe.c | 1
.../ftrace/test.d/dynevent/add_remove_btfarg.tc | 14 +
.../ftrace/test.d/dynevent/fprobe_syntax_errors.tc | 6
11 files changed, 582 insertions(+), 173 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2023-07-26 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 12:59 Masami Hiramatsu (Google) [this message]
2023-07-26 13:00 ` [PATCH v3 1/9] tracing/probes: Support BTF argument on module functions Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 2/9] bpf/btf: tracing: Move finding func-proto API and getting func-param API to BTF Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 3/9] bpf/btf: Add a function to search a member of a struct/union Masami Hiramatsu (Google)
2023-07-27 15:39 ` Alexei Starovoitov
2023-07-28 0:09 ` Masami Hiramatsu
2023-07-26 13:00 ` [PATCH v3 4/9] tracing/probes: Support BTF based data structure field access Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 5/9] tracing/probes: Support BTF field access from $retval Masami Hiramatsu (Google)
2023-07-26 22:53 ` Masami Hiramatsu
2023-07-27 1:59 ` [PATCH 5/9 v3.1] " Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 6/9] tracing/probes: Add string type check with BTF Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 7/9] tracing/fprobe-event: Assume fprobe is a return event by $retval Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 8/9] selftests/ftrace: Add BTF fields access testcases Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 9/9] Documentation: tracing: Update fprobe event example with BTF field 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=169037639315.607919.2613476171148037242.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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 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.