All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Thomas Richter <tmricht@linux.ibm.com>,
	Howard Chu <howardchu95@gmail.com>
Subject: Re: [PATCH] perf trace: Skip internal syscall arguments
Date: Sat, 29 Nov 2025 12:23:01 -0800	[thread overview]
Message-ID: <aStWJTF4WOVFkSG1@google.com> (raw)
In-Reply-To: <20251129144202.0567743b@robin>

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@kernel.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@goodmis.org>

Thanks, I think it's a separate issue.  Will take a look.

Namhyung


  reply	other threads:[~2025-11-29 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27  4:44 [PATCH] perf trace: Skip internal syscall arguments Namhyung Kim
2025-11-27  7:10 ` Thomas Richter
2025-11-27 19:47   ` Howard Chu
2025-11-28  1:30 ` Steven Rostedt
2025-11-29 19:07   ` Namhyung Kim
2025-11-29 19:42     ` Steven Rostedt
2025-11-29 20:23       ` Namhyung Kim [this message]
2025-12-02  4:09 ` Namhyung Kim

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=aStWJTF4WOVFkSG1@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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.