From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Leo Yan <leo.yan@arm.com>, James Clark <james.clark@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Weilin Wang <weilin.wang@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Dominique Martinet <asmadeus@codewreck.org>,
Yicong Yang <yangyicong@hisilicon.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Add support for cpu event term
Date: Fri, 4 Apr 2025 10:09:27 -0400 [thread overview]
Message-ID: <c21d05c6-d71c-47e3-b4a2-e275d9d487f2@linux.intel.com> (raw)
In-Reply-To: <20250403194337.40202-1-irogers@google.com>
On 2025-04-03 3:43 p.m., Ian Rogers 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.
>
> v6: Purely a rebase.
> 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
> on
Tried on a Hybrid platform. Everything looks good.
Tested-by: Kan Liang <kan.liang@linux.intel.com>
Thanks,
Kan>
> tools/lib/perf/cpumap.c | 10 +++
> tools/lib/perf/include/perf/cpumap.h | 2 +
> tools/perf/Documentation/perf-list.txt | 9 ++
> tools/perf/util/evsel_config.h | 1 +
> tools/perf/util/parse-events.c | 113 ++++++++++++++++++-------
> tools/perf/util/parse-events.h | 3 +-
> tools/perf/util/parse-events.l | 1 +
> tools/perf/util/pmu.c | 3 +-
> tools/perf/util/stat-display.c | 21 +++--
> 9 files changed, 124 insertions(+), 39 deletions(-)
>
prev parent reply other threads:[~2025-04-04 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 19:43 [PATCH v6 0/4] Add support for cpu event term Ian Rogers
2025-04-03 19:43 ` [PATCH v6 1/4] libperf cpumap: Add ability to create CPU from a single CPU number Ian Rogers
2025-04-03 19:43 ` [PATCH v6 2/4] perf stat: Use counter cpumask to skip zero values Ian Rogers
2025-04-03 19:43 ` [PATCH v6 3/4] perf parse-events: Set is_pmu_core for legacy hardware events Ian Rogers
2025-04-03 19:43 ` [PATCH v6 4/4] perf parse-events: Add "cpu" term to set the CPU an event is recorded on Ian Rogers
2025-04-04 14:09 ` Liang, Kan [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=c21d05c6-d71c-47e3-b4a2-e275d9d487f2@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=weilin.wang@intel.com \
--cc=yangyicong@hisilicon.com \
/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;
as well as URLs for NNTP newsgroup(s).