From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>, Yonghong Song <yhs@fb.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
bpf@vger.kernel.org, Joel Fernandes <joel@joelfernandes.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] tracing: Allow system call tracepoints to handle page faults
Date: Fri, 4 Oct 2024 10:49:36 -0400 [thread overview]
Message-ID: <1aff8385-083e-4d8d-9c81-ce8d54b688ed@efficios.com> (raw)
In-Reply-To: <20241004011201.1681962-1-mathieu.desnoyers@efficios.com>
On 2024-10-04 03:11, Mathieu Desnoyers wrote:
> Wire up the system call tracepoints with Tasks Trace RCU to allow
> the ftrace, perf, and eBPF tracers to handle page faults.
>
> This series does the initial wire-up allowing tracers to handle page
> faults, but leaves out the actual handling of said page faults as future
> work.
>
> This series was compile and runtime tested with ftrace and perf syscall
> tracing and raw syscall tracing, adding a WARN_ON_ONCE() in the
> generated code to validate that the intended probes are used for raw
> syscall tracing. The might_fault() added within those probes validate
> that they are called from a context where handling a page fault is OK.
>
> This series replaces the "Faultable Tracepoints v6" series found at [1].
>
> This has been rebased on v6.12-rc1 on top of two patches from Steven:
>
> tracing: Remove definition of trace_*_rcuidle()
> tracepoint: Remove SRCU protection
I'll send an updated series which includes
"tracing: Declare system call tracepoints with TRACE_EVENT_SYSCALL"
(missing here), and which rework that patch to remove the mapping from
trace_sys_enter/exit to trace_syscall_sys_enter/exit which requires
modifying architecture code. A lot of churn for little value add.
Thanks,
Mathieu
>
> Thanks,
>
> Mathieu
>
> Link: https://lore.kernel.org/lkml/20240828144153.829582-1-mathieu.desnoyers@efficios.com/ # [1]
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Yonghong Song <yhs@fb.com>
> Cc: Paul E. McKenney <paulmck@kernel.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
> Cc: bpf@vger.kernel.org
> Cc: Joel Fernandes <joel@joelfernandes.org>
> Cc: linux-trace-kernel@vger.kernel.org
>
> Mathieu Desnoyers (7):
> tracing/ftrace: guard syscall probe with preempt_notrace
> tracing/perf: guard syscall probe with preempt_notrace
> tracing/bpf: guard syscall probe with preempt_notrace
> tracing: Allow system call tracepoints to handle page faults
> tracing/ftrace: Add might_fault check to syscall probes
> tracing/perf: Add might_fault check to syscall probes
> tracing/bpf: Add might_fault check to syscall probes
>
> include/linux/tracepoint.h | 18 ++++++++++-----
> include/trace/bpf_probe.h | 12 +++++++++-
> include/trace/perf.h | 42 +++++++++++++++++++++++++++++++----
> include/trace/trace_events.h | 39 ++++++++++++++++++++++++++------
> init/Kconfig | 1 +
> kernel/trace/trace_syscalls.c | 28 +++++++++++++++++++++++
> 6 files changed, 123 insertions(+), 17 deletions(-)
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2024-10-04 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 1:11 [PATCH v2 0/7] tracing: Allow system call tracepoints to handle page faults Mathieu Desnoyers
2024-10-04 1:11 ` [PATCH v2 1/7] tracing/ftrace: guard syscall probe with preempt_notrace Mathieu Desnoyers
2024-10-04 1:11 ` [PATCH v2 2/7] tracing/perf: " Mathieu Desnoyers
2024-10-04 1:11 ` [PATCH v2 3/7] tracing/bpf: " Mathieu Desnoyers
2024-10-04 1:11 ` [PATCH v2 4/7] tracing: Allow system call tracepoints to handle page faults Mathieu Desnoyers
2024-10-04 1:11 ` [PATCH v2 5/7] tracing/ftrace: Add might_fault check to syscall probes Mathieu Desnoyers
2024-10-04 1:12 ` [PATCH v2 6/7] tracing/perf: " Mathieu Desnoyers
2024-10-04 1:12 ` [PATCH v2 7/7] tracing/bpf: " Mathieu Desnoyers
2024-10-04 14:49 ` Mathieu Desnoyers [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=1aff8385-083e-4d8d-9c81-ce8d54b688ed@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yhs@fb.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