linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Howard Chu <howardchu95@gmail.com>,
	Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	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
Subject: Re: [PATCH] perf test: Add cgroup summary test case for perf trace
Date: Fri, 23 May 2025 15:12:48 -0700	[thread overview]
Message-ID: <aDDy4FQe7sBwECL8@google.com> (raw)
In-Reply-To: <aC-hHTgArwlF_zu9@x1>

On Thu, May 22, 2025 at 07:11:41PM -0300, Arnaldo Carvalho de Melo wrote:
> On Thu, May 22, 2025 at 01:49:37PM -0300, Arnaldo Carvalho de Melo wrote:
> > On Thu, May 22, 2025 at 08:33:16AM -0700, Howard Chu wrote:
> > > $ sudo /tmp/perf/perf test -vv 112
> > > 112: perf trace summary:
> > > 112: perf trace summary
> > > --- start ---
> > > test child forked, pid 1574993
> > > testing: perf trace -s -- true
> > > testing: perf trace -S -- true
> > > testing: perf trace -s --summary-mode=thread -- true
> > > testing: perf trace -S --summary-mode=total -- true
> > > testing: perf trace -as --summary-mode=thread --no-bpf-summary -- true
> > > testing: perf trace -as --summary-mode=total --no-bpf-summary -- true
> > > testing: perf trace -as --summary-mode=thread --bpf-summary -- true
> > > testing: perf trace -as --summary-mode=total --bpf-summary -- true
> > > testing: perf trace -aS --summary-mode=total --bpf-summary -- true
> > > testing: perf trace -as --summary-mode=cgroup --bpf-summary -- true
> > > testing: perf trace -aS --summary-mode=cgroup --bpf-summary -- true
> > > ---- end(0) ----
> > > 112: perf trace summary                                              : Ok
>  
> > Thanks, tested and applied to perf-tools-next,
> 
> But then when running all the tests, since this does system wide
> tracing, it fails:
> 
> 112: perf trace summary                                              : FAILED!
> 
> It works with the following patch applied, please check and ack/review:
> 
> From 8c868979d886e2e88aa89f4e3d884e1b6450a7b2 Mon Sep 17 00:00:00 2001
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Thu, 22 May 2025 19:01:47 -0300
> Subject: [PATCH 1/1] perf tests trace_summary.sh: Run in exclusive mode
> 
> And it is being successfull only when running alone, probably because
> there are some tests that add the vfs_getname probe that gets used by
> 'perf trace' and alter how it does syscall arg pathname resolution.
> 
> This should be removed or made a fallback to the preferred BPF mode of
> getting syscall parameters, but till then, run this in exclusive mode.
> 
> For reference, here are some of the tests that run close to this one:
> 
>   127: perf record offcpu profiling tests                              : Ok
>   128: perf all PMU test                                               : Ok
>   129: perf stat --bpf-counters test                                   : Ok
>   130: Check Arm CoreSight trace data recording and synthesized samples: Skip
>   131: Check Arm CoreSight disassembly script completes without errors : Skip
>   132: Check Arm SPE trace data recording and synthesized samples      : Skip
>   133: Test data symbol                                                : Ok
>   134: Miscellaneous Intel PT testing                                  : Skip
>   135: test Intel TPEBS counting mode                                  : Skip
>   136: perf script task-analyzer tests                                 : Ok
>   137: Check open filename arg using perf trace + vfs_getname          : Ok
>   138: perf trace summary                                              : Ok
> 
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Howard Chu <howardchu95@gmail.com>
> Cc: Ian Rogers <irogers@google.com>
> Cc: James Clark <james.clark@linaro.org>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Kan Liang <kan.liang@linux.intel.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

Looks good to me.

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung

> ---
>  tools/perf/tests/shell/trace_summary.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/tests/shell/trace_summary.sh b/tools/perf/tests/shell/trace_summary.sh
> index bb350dfabdc2bf5e..49766524dc21b534 100755
> --- a/tools/perf/tests/shell/trace_summary.sh
> +++ b/tools/perf/tests/shell/trace_summary.sh
> @@ -1,5 +1,5 @@
>  #!/bin/sh
> -# perf trace summary
> +# perf trace summary (exclusive)
>  # SPDX-License-Identifier: GPL-2.0
>  
>  # Check that perf trace works with various summary mode
> -- 
> 2.49.0
> 

  parent reply	other threads:[~2025-05-23 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 14:25 [PATCH] perf test: Add cgroup summary test case for perf trace Namhyung Kim
2025-05-22 15:33 ` Howard Chu
2025-05-22 16:49   ` Arnaldo Carvalho de Melo
2025-05-22 22:11     ` Arnaldo Carvalho de Melo
2025-05-23  0:48       ` Howard Chu
2025-05-23 22:12       ` Namhyung Kim [this message]
2025-05-29  6:59         ` Howard Chu
2025-05-29 20:46           ` Arnaldo Carvalho de Melo
2025-05-30 17:12             ` Howard Chu

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=aDDy4FQe7sBwECL8@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).