From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"acme@kernel.org" <acme@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"irogers@google.com" <irogers@google.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>
Cc: "ravi.bangoria@amd.com" <ravi.bangoria@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH v2] perf script: Fix output type for dynamically allocated core PMU's
Date: Fri, 13 Dec 2024 20:39:56 +0000 [thread overview]
Message-ID: <82cb71b5deab913dbe85504882b03c84bdf55137.camel@intel.com> (raw)
In-Reply-To: <219e5f79-d2c2-45df-9298-142597ebb404@linux.intel.com>
On Fri, 2024-12-13 at 15:21 -0500, Liang, Kan wrote:
>
>
> On 2024-12-13 3:11 p.m., Thomas Falcon wrote:
> > perf script output may show different fields on different core
> > PMU's
> > that exist on heterogeneous platforms. For example,
> >
> > perf record -e "{cpu_core/mem-loads-aux/,cpu_core/event=0xcd,\
> > umask=0x01,ldlat=3,name=MEM_UOPS_RETIRED.LOAD_LATENCY/}:upp"\
> > -c10000 -W -d -a -- sleep 1
> >
> > perf script:
> >
> > chromium-browse 46572 [002] 544966.882384:
> > 10000 cpu_core/MEM_UOPS_RETIRED.LOAD_LATENCY/: 7ffdf1391b0c 10268100142\
> > |OP LOAD|LVL L1 hit|SNP None|TLB L1 or L2 hit|LCK No|BLK N/A
> > 5 7 0 7fad7c47425d [unknown] (/usr/lib64/libglib-
> > 2.0.so.0.8000.3)
> >
> > perf record -e cpu_atom/event=0xd0,umask=0x05,ldlat=3,\
> > name=MEM_UOPS_RETIRED.LOAD_LATENCY/upp -c10000 -W -d -a -- sleep 1
> >
> > perf script:
> >
> > gnome-control-c 534224 [023] 544951.816227: 10000
> > cpu_atom/MEM_UOPS_RETIRED.LOAD_LATENCY/: 7f0aaaa0aae0 [unknown]
> > (/usr/lib64/libglib-2.0.so.0.8000.3)
> >
> > Some fields, such as data_src, are not included by default.
> >
> > The cause is that while one PMU may be assigned a type such as
> > PERF_TYPE_RAW, other core PMU's are dynamically allocated at boot
> > time.
> > If this value does not match an existing PERF_TYPE_X value,
> > output_type(perf_event_attr.type) will return OUTPUT_TYPE_OTHER.
> >
> > Instead search for a core PMU with a matching perf_event_attr type
> > and, if one is found, return PERF_TYPE_RAW to match output of other
> > core PMU's.
> >
> > Suggested-by: Kan Liang <kan.liang@intel.com>
> > Signed-off-by: Thomas Falcon <thomas.falcon@intel.com>
> > ---
> > v2: restrict pmu lookup to platforms with more than one core pmu
> > ---
> > tools/perf/builtin-script.c | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-
> > script.c
> > index 9e47905f75a6..459794c737ce 100644
> > --- a/tools/perf/builtin-script.c
> > +++ b/tools/perf/builtin-script.c
> > @@ -384,6 +384,18 @@ static int evsel_script__fprintf(struct
> > evsel_script *es, FILE *fp)
> > st.st_size / 1024.0 / 1024.0, es->filename,
> > es->samples);
> > }
> >
> > +static bool output_type_many_core_pmus(unsigned int type)
> > +{
> > + struct perf_pmu *pmu;
> > +
> > + if (perf_pmus__num_core_pmus() > 1) {
> > + pmu = perf_pmus__find_by_type(type);
> > + if (pmu && pmu->is_core)>
> > + return true;
>
> I think it should be good enough to search the core_pmus.
> list_for_each_entry(pmu, &core_pmus, list) {
> if (pmu->type == type)
> return true;
> }
>
> Thanks,
> Kan
Thanks, will resend with your changes.
Tom
> > + }
> > + return false;
> > +}
> > +
> > static inline int output_type(unsigned int type)
> > {
> > switch (type) {
> > @@ -394,6 +406,9 @@ static inline int output_type(unsigned int
> > type)
> > return type;
> > }
> >
> > + if (output_type_many_core_pmus(type))
> > + return PERF_TYPE_RAW;
> > +
> > return OUTPUT_TYPE_OTHER;
> > }
> >
>
prev parent reply other threads:[~2024-12-13 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 20:11 [PATCH v2] perf script: Fix output type for dynamically allocated core PMU's Thomas Falcon
2024-12-13 20:21 ` Liang, Kan
2024-12-13 20:39 ` Falcon, Thomas [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=82cb71b5deab913dbe85504882b03c84bdf55137.camel@intel.com \
--to=thomas.falcon@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.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=ravi.bangoria@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.