[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aStWJTF4WOVFkSG1@google.com>
Date: Sat, 29 Nov 2025 12:23:01 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>,
James Clark <james.clark@...aro.org>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Thomas Richter <tmricht@...ux.ibm.com>,
Howard Chu <howardchu95@...il.com>
Subject: Re: [PATCH] perf trace: Skip internal syscall arguments
On Sat, Nov 29, 2025 at 02:42:02PM -0500, Steven Rostedt wrote:
> On Sat, 29 Nov 2025 11:07:20 -0800
> Namhyung Kim <namhyung@...nel.org> wrote:
>
> > > Even with this patch applied, I still have a segfault with this command:
> > >
> > > # ./perf trace -e syscalls:sys_enter_write
> >
> > What about this?
> >
> > # ./perf trace -e write
>
> Yes that works. As long as it isn't considered a regression that the
> sys_enter_write crashes, then I'm fine with;
>
> Tested-by: Steven Rostedt (Google) <rostedt@...dmis.org>
Thanks, I think it's a separate issue. Will take a look.
Namhyung
Powered by blists - more mailing lists