From: Steven Rostedt <rostedt@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Brian Geffon <bgeffon@google.com>,
John Stultz <jstultz@google.com>, Ian Rogers <irogers@google.com>,
Suleiman Souhlal <suleiman@google.com>
Subject: Re: [PATCH 1/2] tracing: Have futex syscall trace event show specific user data
Date: Wed, 4 Mar 2026 20:37:44 -0500 [thread overview]
Message-ID: <20260304203744.02e76dff@fedora> (raw)
In-Reply-To: <20260304090748.GO606826@noisy.programming.kicks-ass.net>
On Wed, 4 Mar 2026 10:07:48 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Mar 03, 2026 at 04:47:36PM -0500, Steven Rostedt wrote:
> > From: Steven Rostedt <rostedt@goodmis.org>
> >
> > Add specific reporting of the futex system call. This allows for debugging
> > the futex code a bit easier. Instead of just showing the values passed
> > into the futex system call, read the value of the user space memory
> > pointed to by the addr parameter.
> >
> > Also make the op parameter more readable by parsing the values to show
> > what the command is:
> >
> > futex_requeue_p-3251 [002] ..... 2101.068479: sys_futex(uaddr: 0x55e79a4da834 (0x80000cb1), FUTEX_LOCK_PI|FUTEX_PRIVATE_FLAG, val: 0)
> > futex_requeue_p-3248 [001] ..... 2101.068970: sys_futex(uaddr: 0x7f859072f990 (0xcb2), FUTEX_WAIT_BITSET|FUTEX_CLOCK_REALTIME, val: 3250)
> > futex_requeue_p-3252 [005] ..... 2101.069108: sys_futex(uaddr: 0x55e79a4da838 (0), FUTEX_WAIT_REQUEUE_PI|FUTEX_PRIVATE_FLAG, val: 0, timespec: 0x7ffe61076aa0, uaddr2: 0x55e79a4da834, uaddr2: 94453214586932, val3: 0)
> > futex_requeue_p-3252 [005] ..... 2101.069410: sys_futex(uaddr: 0x55e79a4da834 (0x80000cb1), FUTEX_LOCK_PI|FUTEX_PRIVATE_FLAG, val: 0)
> >
> > Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> > ---
> > kernel/trace/trace_syscalls.c | 266 +++++++++++++++++++++++++++++++++-
> > 1 file changed, 263 insertions(+), 3 deletions(-)
>
> Egads, I really dislike how all sorts of syscall crud is 'duplicated' in
> this file, rather than near or in the actual syscall definition.
Now I did copy the futex_cmd_has_timeout() which I could just use the
futex one by exporting it. But the rest is due to printing the content.
What exactly is "duplicated"? The code is mostly done to display the
data, where as the futex syscall code is about implementing it.
What do you suggest in reuse? Or just move some of theses functions
into kernel/futex/syscall.c?
-- Steve
next prev parent reply other threads:[~2026-03-05 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 21:47 [PATCH 0/2] tracing: Read user data from futex system call trace event Steven Rostedt
2026-03-03 21:47 ` [PATCH 1/2] tracing: Have futex syscall trace event show specific user data Steven Rostedt
2026-03-04 9:07 ` Peter Zijlstra
2026-03-05 1:37 ` Steven Rostedt [this message]
2026-03-03 21:47 ` [PATCH 2/2] tracing: Update futex syscall trace event to show more commands Steven Rostedt
2026-03-03 22:44 ` [PATCH 3/2] tracing: Show TID and flags for PI futex system call trace event Steven Rostedt
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=20260304203744.02e76dff@fedora \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=irogers@google.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=suleiman@google.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