From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-perf-users@vger.kernel.org, acme@kernel.org,
agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com
Subject: Re: [PATCH Linux-next] perf test: Fix test case perf trace BTF general tests
Date: Wed, 19 Nov 2025 16:52:28 -0800 [thread overview]
Message-ID: <aR5mTLRWA-SLAFUM@google.com> (raw)
In-Reply-To: <20251119125903.417f595e@gandalf.local.home>
On Wed, Nov 19, 2025 at 12:59:03PM -0500, Steven Rostedt wrote:
> On Tue, 18 Nov 2025 20:36:46 -0800
> Namhyung Kim <namhyung@kernel.org> wrote:
>
> > > Really? It still uses libtraceevent right? I made sure that this didn't
> > > break trace-cmd and thought that perf would work too.
> >
> > It doesn't completely break perf trace but added new parameter for the
> > write syscall at the end. IIUC perf trace iterates the format fields
> > after __syscall_nr and take them all as syscall parameters.
>
> Is this a regression? Or can perf be fixed?
>
> I just ran it and I have this:
>
> 542.337 ( 0.131 ms): sshd-session/1189 write(fd: 7<socket:[9749]>, buf: , count: 268) = 268
>
> I haven't tried it without the patches. Does it usually show what "buf" is?
> Now with the reading of user space, it can show the content too!
Yep, it reads the content using BPF. This is on my 6.16 kernel.
$ sudo perf trace -e write -- /bin/echo hello
hello
0.000 ( 0.014 ms): echo/61922 write(fd: 1, buf: hello\10, count: 6) = 6
Thanks,
Namhyung
next prev parent reply other threads:[~2025-11-20 0:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:43 [PATCH Linux-next] perf test: Fix test case perf trace BTF general tests Thomas Richter
2025-11-18 1:58 ` Namhyung Kim
2025-11-18 6:15 ` Thomas Richter
2025-11-18 6:43 ` Namhyung Kim
2025-11-18 18:24 ` Steven Rostedt
2025-11-19 4:36 ` Namhyung Kim
2025-11-19 17:59 ` Steven Rostedt
2025-11-20 0:52 ` Namhyung Kim [this message]
2025-11-26 7:13 ` Thomas Richter
2025-11-26 15:24 ` Steven Rostedt
2025-11-26 17:12 ` Steven Rostedt
2025-11-26 17:37 ` Steven Rostedt
2025-11-26 18:57 ` Namhyung Kim
2025-11-26 19:01 ` Howard Chu
2025-11-27 6:28 ` Thomas Richter
2025-11-18 18:30 ` Jan Polensky
2025-11-19 7:55 ` Thomas Richter
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=aR5mTLRWA-SLAFUM@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=japo@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@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.