Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1] perf test switch-tracking: Fix hybrid cpu-cycles and spin timing
Date: Sun, 25 Oct 2026 22:22:00 +0000	[thread overview]
Message-ID: <sashiko-outbox-184473@kernel.org> (raw)
In-Reply-To: <20261025215056.1228120-1-irogers@google.com>

> On hybrid systems, parse_event(evlist, "cpu-cycles:u") creates multiple
> evsels (e.g. cpu_atom/cpu-cycles/ and cpu_core/cpu-cycles/), but
> test__switch_tracking() only configured, enabled/disabled, and checked
> evlist__last(evlist). If the test process ran on another core PMU during
> one of the spin phases, the tracked evsel recorded no samples and the
> test failed with 'Missing cycles events'. Additionally, the other core
> PMU evsels did not have PERF_SAMPLE_TIME set, which add_event() missed
> because __evsel__parse_sample() initializes sample.time to -1ULL rather
> than 0.
> 
> Use evsel__match(evsel, HARDWARE, HW_CPU_CYCLES) to configure,
> enable/disable, and check all cycles evsels created by parse_event(),
> check for sample.time == -1ULL in add_event(), and use
> CLOCK_THREAD_CPUTIME_ID in spin_sleep() so preemption under load does
> not finish the 50ms spin without on-CPU cycles.
> 
> Fixes: 94f9eb95d954 ("perf pmus: Remove perf_pmus__has_hybrid")
> Signed-off-by: Ian Rogers <irogers@google.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261025215056.1228120-1-irogers@google.com?part=1


      reply	other threads:[~2026-10-25 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 21:50 [PATCH v1] perf test switch-tracking: Fix hybrid cpu-cycles and spin timing Ian Rogers
2026-10-25 22:22 ` 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-184473@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=irogers@google.com \
    --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