linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	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 1/2] perf test: Fix LBR test by ignoring idle task
Date: Tue, 13 May 2025 07:58:07 -0700	[thread overview]
Message-ID: <CAP-5=fVQ1L2yD3F+XLg4-U57wVVDFhkfb3QRD34ie01JjmijJQ@mail.gmail.com> (raw)
In-Reply-To: <20250509213017.204343-1-namhyung@kernel.org>

On Fri, May 9, 2025 at 2:30 PM Namhyung Kim <namhyung@kernel.org> wrote:
>
> I found 'perf record LBR tests' failing due to empty branch stacks.
>
>   $ perf test -v LBR
>   ...
>   LBR system wide any branch test
>   Lowering default frequency rate from 4000 to 1000.
>   Please consider tweaking /proc/sys/kernel/perf_event_max_sample_rate.
>   [ perf record: Woken up 8 times to write data ]
>   [ perf record: Captured and wrote 3.142 MB /tmp/__perf_test.perf.data.dgSBl (3572 samples) ]
>   LBR system wide any branch test: 3572 samples
>   LBR system wide any branch test [Failed empty br stack ratio exceed 2%: 3%]
>   LBR system wide any call test
>   Lowering default frequency rate from 4000 to 1000.
>   Please consider tweaking /proc/sys/kernel/perf_event_max_sample_rate.
>   [ perf record: Woken up 8 times to write data ]
>   [ perf record: Captured and wrote 3.337 MB /tmp/__perf_test.perf.data.dgSBl (3967 samples) ]
>   LBR system wide any call test: 3967 samples
>   LBR system wide any call test [Failed empty br stack ratio exceed 2%: 9%]
>   ...
>
> The failing cases were in system-wide mode and I realized that the
> samples were from the idle tasks (swapper).  I suspect going to/from
> idle state may affect the LBR contents.
>
> If we can skip empty branch stacks from the idle tasks, the failure
> should go away.  I can see the following output in perf report -D.
>
>   $ perf report -D | grep -m5 -A3 'branch stack: nr:0'
>   ...
>   --
>   ... branch stack: nr:0
>    ... thread: swapper:0
>    ...... dso: /proc/kcore
>
>   --
>   ... branch stack: nr:0
>    ... thread: swapper:0
>    ...... dso: /proc/kcore
>
>   --
>   ... branch stack: nr:0
>    ... thread: DefaultEventMan:10282
>    ...... dso: /proc/kcore
>
>   --
>   ... branch stack: nr:0
>    ... thread: swapper:0
>    ...... dso: /proc/kcore
>
>   --
>   ... branch stack: nr:0
>    ... thread: swapper:0
>    ...... dso: /proc/kcore
>
>   $ perf report -D | grep -c 'branch stack: nr:0'
>   145
>
>   $ perf report -D | grep -A3 'branch stack: nr:0' | grep thread | grep -c swapper
>   i36
>
>   $ perf report -D | grep -A3 'branch stack: nr:0' | grep thread | grep -cv swapper
>   9
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>

Reviewed-by: Ian Rogers <irogers@google.com>

Thanks,
Ian

> ---
>  tools/perf/tests/shell/record_lbr.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/shell/record_lbr.sh b/tools/perf/tests/shell/record_lbr.sh
> index 8d750ee631f877fd..afad02d0180e023c 100755
> --- a/tools/perf/tests/shell/record_lbr.sh
> +++ b/tools/perf/tests/shell/record_lbr.sh
> @@ -93,7 +93,7 @@ lbr_test() {
>      return
>    fi
>
> -  zero_nr=$(echo "$out" | grep -c 'branch stack: nr:0' || true)
> +  zero_nr=$(echo "$out" | grep -A3 'branch stack: nr:0' | grep thread | grep -cv swapper || true)
>    r=$(($zero_nr * 100 / $bs_nr))
>    if [ $r -gt $threshold ]; then
>      echo "$test [Failed empty br stack ratio exceed $threshold%: $r%]"
> --
> 2.49.0.1015.ga840276032-goog
>

  parent reply	other threads:[~2025-05-13 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 21:30 [PATCH 1/2] perf test: Fix LBR test by ignoring idle task Namhyung Kim
2025-05-09 21:30 ` [PATCH 2/2] perf test: Update sysfs path for core PMU caps Namhyung Kim
2025-05-13 14:58   ` Ian Rogers
2025-05-13 20:46     ` Arnaldo Carvalho de Melo
2025-05-13 14:58 ` Ian Rogers [this message]
2025-05-13 20:46   ` [PATCH 1/2] perf test: Fix LBR test by ignoring idle task Arnaldo Carvalho de Melo

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='CAP-5=fVQ1L2yD3F+XLg4-U57wVVDFhkfb3QRD34ie01JjmijJQ@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.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=namhyung@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).