From: sashiko-bot@kernel.org
To: "James Clark" <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 4/4] perf test: Don't starve per-process tests with system-wide events
Date: Fri, 06 Nov 2026 10:51:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-201234@kernel.org> (raw)
In-Reply-To: <20261106-james-perf-test-fixes-v2-4-9a912662f822@linaro.org>
> Some tests intermittently fail when run in parallel, for example "Check
> branch stack sampling" fails with no branches recorded at all.
>
> The default event is cycles:P which there may only be 1 or 2 HW counters
> for on Intel because it's precise. System wide or per-core precise
> events hog the HW counter leaving other per-process tests with no
> samples. Rather than make all the tests that use default record commands
> run serially, just make the system wide ones use a software event which
> has the greatest possible compatibility. They don't need precise
> sampling or HW counters anyway. The per-process tests can be left alone
> as their events/processes never run concurrently on any one core.
>
> The LBR filter is another resource shared by all events on a CPU, and
> the system-wide LBR test uses different filters to the per-process
> branch stack test, so mark the LBR test as exclusive.
> [ ... ]
> ...
> ---- end(-1) ----
> 138: Check branch stack sampling : FAILED!
>
> Signed-off-by: James Clark <james.clark@linaro.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106-james-perf-test-fixes-v2-0-9a912662f822@linaro.org?part=4
prev parent reply other threads:[~2026-11-06 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 10:48 [PATCH v2 0/4] perf tools: LLVM dwarf and flaky test fixes James Clark
2026-11-06 10:48 ` [PATCH v2 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-06 10:57 ` sashiko-bot
2026-11-06 10:48 ` [PATCH v2 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-06 10:52 ` sashiko-bot
2026-11-06 10:48 ` [PATCH v2 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-06 10:53 ` sashiko-bot
2026-11-06 10:48 ` [PATCH v2 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
2026-11-06 10:51 ` sashiko-bot [this message]
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=sashiko-outbox-201234@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=james.clark@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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