[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP-5=fVH=HN0csS6cXLPAYdk7Vn-g8FSdKWkaHcjfYKRA1o1Ag@mail.gmail.com>
Date: Mon, 17 Mar 2025 09:22:43 -0700
From: Ian Rogers <irogers@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, 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>,
Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, Leo Yan <leo.yan@....com>,
Yoshihiro Furudera <fj5100bi@...itsu.com>, Weilin Wang <weilin.wang@...el.com>,
Andi Kleen <ak@...ux.intel.com>, James Clark <james.clark@...aro.org>,
Dominique Martinet <asmadeus@...ewreck.org>, Yicong Yang <yangyicong@...ilicon.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/4] Add support for cpu event term
On Mon, Feb 10, 2025 at 10:38 AM Ian Rogers <irogers@...gle.com> wrote:
>
> Being able to set the cpu mask per event was discussed in the context
> of a sysfs event.cpus file is discussed here:
> https://lore.kernel.org/lkml/CAP-5=fXXuWchzUK0n5KTH8kamr=DQoEni+bUoo8f-4j8Y+eMBg@mail.gmail.com/
> Ultimately Kan preferred to have multiple PMUs with a cpumask each
> rather than an event.cpus file per event. It is still useful to have
> the cpu event term and so the sysfs part of the original patch series
> is dropped.
>
> v5: Purely a rebase.
> v4: Add the stat-display output change for zero counters Namhyung
> requested as part of the series:
> https://lore.kernel.org/lkml/Zvx9VbJWtmkcuSBs@google.com/
> This skips zero values for CPUs not in the evsel's cpumask rather
> than the evsel's PMU's cpumask.
> v3: Drop sysfs event.cpus file support patch from series. Reference
> to using cpu to modify uncore events is dropped from the commit
> message. Reference counting issues on the cpumap are addressed.
> v2: Add support for multiple cpu terms on an event that are
> merged. For example, an event of "l1d-misses/cpu=4,cpu=5/" will
> now be opened on both CPU 4 and 5 rather than just CPU 4.
>
> Ian Rogers (4):
> libperf cpumap: Add ability to create CPU from a single CPU number
> perf stat: Use counter cpumask to skip zero values
> perf parse-events: Set is_pmu_core for legacy hardware events
> perf parse-events: Add "cpu" term to set the CPU an event is recorded
Ping.
Thanks,
Ian
Powered by blists - more mailing lists