[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31ad367a-721f-46e7-8e5f-e96b250a8a32@linux.intel.com>
Date: Mon, 20 Jan 2025 11:44:37 -0500
From: "Liang, Kan" <kan.liang@...ux.intel.com>
To: Vince Weaver <vincent.weaver@...ne.edu>, peterz@...radead.org
Cc: Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo
<acme@...nel.org>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: perf: is it possible to userspace rdpmc but only on a certain
core type
On 2025-01-17 5:04 p.m., Vince Weaver wrote:
> Hello
>
> so we've been working on PAPI support for Intel Top-Down events, which
> let's say does "exciting" things involving the rdpmc instruction.
>
> One issue we are having is that on a hybrid machine (Raptor Lake in this
> case with performance/efficiency cores) there is no top-down support
> for the E-cores, and it will gpf/segfault if you try to rdpmc the top-down
> events.
>
> Obviously PAPI would like to avoid this, and somehow only run the rdpmc
> from userspace if scheduled on a P-core.
>
> Is there any way to atomically do this? Somehow detect what core we are
> on and atomically execute a userspace instruction before a core-reschedule
> can happen?
>
> Or barring that, any other way to handle this in a way that won't crash
> without having to have the users have to bind to a core any time they want
> to run PAPI?
Can the PAPI rely on the event_idx(), similar to what Andi's pmu-tools
do? For a stopped event, the index is always 0.
https://github.com/andikleen/pmu-tools/blob/master/jevents/rdpmc.c#L117
Thanks,
Kan
Powered by blists - more mailing lists