From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Florent Revest <revest@chromium.org>
Cc: linux-trace-kernel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
bpf <bpf@vger.kernel.org>, Sven Schnelle <svens@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alan Maguire <alan.maguire@oracle.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v3 0/8] bpf: fprobe: rethook: Use ftrace_regs instead of pt_regs
Date: Sat, 12 Aug 2023 14:36:35 +0900 [thread overview]
Message-ID: <169181859570.505132.10136520092011157898.stgit@devnote2> (raw)
Hi,
Here is the 3rd version of RFC series to use ftrace_regs instead of pt_regs.
The previous version is here;
https://lore.kernel.org/all/169139090386.324433.6412259486776991296.stgit@devnote2/
This also includes the generic part and minimum modifications of arch
dependent code. (e.g. not including rethook for arm64.) This series is based
on the discussion at
https://lore.kernel.org/all/20230801112036.0d4ee60d@gandalf.local.home/
This version added some documentation updates, fix typos, fix some build errors
on arm64 and s390, rename config name to HAVE_PT_REGS_TO_FTRACE_REGS_CAST, Use
FTRACE_OPS_FL_SAVE_ARGS in fprobe, add ftrace_regs_get_kernel_stack_nth()
and add check HAVE_REGS_AND_STACK_ACCESS_API=y for ftrace_regs APIs.
- Document fix for the current fprobe callback prototype
- Simply replace pt_regs in fprobe_entry_handler with ftrace_regs.
- Expose ftrace_regs even if CONFIG_FUNCTION_TRACER=n.
- Replace pt_regs in rethook and fprobe_exit_handler with ftrace_regs. This
introduce a new HAVE_PT_REGS_TO_FTRACE_REGS_CAST which means ftrace_regs is
just a wrapper of pt_regs (except for arm64, other architectures do this)
- Update fprobe-events to use ftrace_regs natively.
- Introduce ftrace_partial_regs(). (This changes ARM64 which needs a custom
implementation)
- Update bpf multi-kprobe handler use ftrace_partial_regs().
- Update document to new fprobe callbacks.
This series can also be found below branch.
https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git/log/?h=topic/fprobe-ftrace-regs
Thank you,
---
Masami Hiramatsu (Google) (8):
Documentation: probes: Add a new ret_ip callback parameter
fprobe: Use fprobe_regs in fprobe entry handler
tracing: Expose ftrace_regs regardless of CONFIG_FUNCTION_TRACER
fprobe: rethook: Use ftrace_regs in fprobe exit handler and rethook
tracing/fprobe: Enable fprobe events with CONFIG_DYNAMIC_FTRACE_WITH_ARGS
ftrace: Add ftrace_partial_regs() for converting ftrace_regs to pt_regs
bpf: Enable kprobe_multi feature if CONFIG_FPROBE is enabled
Documentations: probes: Update fprobe document to use ftrace_regs
Documentation/trace/fprobe.rst | 18 +++++---
arch/Kconfig | 1
arch/arm64/include/asm/ftrace.h | 11 +++++
arch/loongarch/Kconfig | 1
arch/s390/Kconfig | 1
arch/s390/include/asm/ftrace.h | 4 ++
arch/x86/Kconfig | 1
arch/x86/kernel/rethook.c | 13 +++---
include/linux/fprobe.h | 4 +-
include/linux/ftrace.h | 83 +++++++++++++++++++++++++++++----------
include/linux/rethook.h | 11 +++--
kernel/kprobes.c | 10 ++++-
kernel/trace/Kconfig | 9 ++++
kernel/trace/bpf_trace.c | 14 ++++---
kernel/trace/fprobe.c | 10 ++---
kernel/trace/rethook.c | 16 ++++----
kernel/trace/trace_fprobe.c | 69 +++++++++++++++++++-------------
kernel/trace/trace_probe_tmpl.h | 2 -
lib/test_fprobe.c | 10 ++---
samples/fprobe/fprobe_example.c | 4 +-
20 files changed, 191 insertions(+), 101 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2023-08-12 5:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 5:36 Masami Hiramatsu (Google) [this message]
2023-08-12 5:36 ` [PATCH v3 1/8] Documentation: probes: Add a new ret_ip callback parameter Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-18 10:59 ` Masami Hiramatsu
2023-08-12 5:36 ` [PATCH v3 2/8] fprobe: Use fprobe_regs in fprobe entry handler Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-18 10:56 ` Masami Hiramatsu
2023-08-12 5:37 ` [PATCH v3 3/8] tracing: Expose ftrace_regs regardless of CONFIG_FUNCTION_TRACER Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-18 10:59 ` Masami Hiramatsu
2023-08-12 5:37 ` [PATCH v3 4/8] fprobe: rethook: Use ftrace_regs in fprobe exit handler and rethook Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-18 11:01 ` Masami Hiramatsu
2023-08-12 5:37 ` [PATCH v3 5/8] tracing/fprobe: Enable fprobe events with CONFIG_DYNAMIC_FTRACE_WITH_ARGS Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-18 11:11 ` Masami Hiramatsu
2023-08-17 20:44 ` Alexei Starovoitov
2023-08-18 12:09 ` Masami Hiramatsu
2023-08-12 5:37 ` [PATCH v3 6/8] ftrace: Add ftrace_partial_regs() for converting ftrace_regs to pt_regs Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-12 5:37 ` [PATCH v3 7/8] bpf: Enable kprobe_multi feature if CONFIG_FPROBE is enabled Masami Hiramatsu (Google)
2023-08-17 8:57 ` Florent Revest
2023-08-12 5:38 ` [PATCH v3 8/8] Documentations: probes: Update fprobe document to use ftrace_regs Masami Hiramatsu (Google)
2023-08-17 8:58 ` Florent Revest
2023-08-17 8:57 ` [PATCH v3 0/8] bpf: fprobe: rethook: Use ftrace_regs instead of pt_regs Florent Revest
2023-08-18 13:40 ` Masami Hiramatsu
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=169181859570.505132.10136520092011157898.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=peterz@infradead.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
/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).