Closed tilsche closed 4 months ago
This is in general a problem in two parts:
cpumask
field at all I personally dislike any solution for the latter that implicitly does stuff such as detecting the cpumask
field and then setting up the metric per-CPU. I think there should be some explicit syntax for that.
Consider
uncore_clock/clockticks/
on alderlake. Apparently this event cannot be recorded on a pid, but only on a cpu. So currently, withlo2s
it can only be recorded with-a --userspace-metric-event uncore_clock/clockticks/
. At least-a
should not be necessary, we should automatically chose the right PID/CPU scope.That should be based on
/sys/bus/event_source/devices/*/cpumask
(since Linux 3.7)See also related
perf
commit.