From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices
Date: Wed, 6 Dec 2017 10:47:02 -0300 [thread overview]
Message-ID: <20171206134702.GA12234@kernel.org> (raw)
In-Reply-To: <71db0255-af9b-968a-7baa-238d7146f069@linux.intel.com>
Em Wed, Dec 06, 2017 at 08:30:37AM +0800, Jin, Yao escreveu:
>
>
> On 12/6/2017 2:42 AM, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Dec 05, 2017 at 08:35:22PM +0800, Jin, Yao escreveu:
> > > A quick test with the new patch 'fix_json_v9_2.patch' shows it working.
> >
> > I'll take this as a Tested-by: you, ok?
>
> Hi Arnaldo,
>
> I didn't do a full test for this patch and for the whole patch series.
>
> I just do a quick test and it shows that the regression issue which was
> found in 'perf stat --per-thread' test case is disappear.
>
> If you think it's enough for adding Tested-by, that's fine for me. :)
I guess this addresses at least your previous regression report, so I
think it is warranted, thanks!
- arnaldo
> Thanks
> Jin Yao
>
> > > See the log:
> > >
> > > root at skl:/tmp# perf stat --per-thread -p 10322 -M CPI,IPC
> > > ^C
> > > Performance counter stats for process id '10322':
> > >
> > > vmstat-10322 1,879,654 inst_retired.any #
> > > 0.8 CPI
> > > vmstat-10322 1,565,807 cycles
> > > vmstat-10322 1,879,654 inst_retired.any #
> > > 1.2 IPC
> > > vmstat-10322 1,565,807 cpu_clk_unhalted.thread
> > >
> > > 2.850291804 seconds time elapsed
> > >
> > > Thanks for fixing it quickly.
> > >
> > > Thanks
> > > Jin Yao
> > >
> > > On 12/5/2017 3:23 PM, Jin, Yao wrote:
> > > > Hi,
> > > >
> > > > I applied the diff but it's failed.
> > > >
> > > > jinyao at skl:~/skl-ws/perf-dev/lck-4594/src$ patch -p1 < 1.pat
> > > > patching file tools/perf/util/pmu.c
> > > > patch: **** malformed patch at line 41: *head, struct perf_pmu *pmu)
> > > >
> > > > Could you send the patch as attachment to me in another mail thread?
> > > >
> > > > to yao.jin at linux.intel.com
> > > > cc yao.jin at intel.com
> > > >
> > > > Thanks
> > > > Jin Yao
> > > >
> > > > On 12/5/2017 3:12 PM, Ganapatrao Kulkarni wrote:
> > > > > diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> > > > > index 5ad8a18..57e38fd 100644
> > > > > --- a/tools/perf/util/pmu.c
> > > > > +++ b/tools/perf/util/pmu.c
> > > > > @@ -538,6 +538,34 @@ static bool pmu_is_uncore(const char *name)
> > > > > ? }
> > > > >
> > > > > ? /*
> > > > > + *? PMU CORE devices have different name other than cpu in sysfs on some
> > > > > + *? platforms. looking for possible sysfs files to identify as core
> > > > > device.
> > > > > + */
> > > > > +static int is_pmu_core(const char *name)
> > > > > +{
> > > > > + struct stat st;
> > > > > + char path[PATH_MAX];
> > > > > + const char *sysfs = sysfs__mountpoint();
> > > > > +
> > > > > + if (!sysfs)
> > > > > + return 0;
> > > > > +
> > > > > + /* Look for cpu sysfs (x86 and others) */
> > > > > + scnprintf(path, PATH_MAX, "%s/bus/event_source/devices/cpu", sysfs);
> > > > > + if ((stat(path, &st) == 0) &&
> > > > > + (strncmp(name, "cpu", strlen("cpu")) == 0))
> > > > > + return 1;
> > > > > +
> > > > > + /* Look for cpu sysfs (specific to arm) */
> > > > > + scnprintf(path, PATH_MAX, "%s/bus/event_source/devices/%s/cpus",
> > > > > + sysfs, name);
> > > > > + if (stat(path, &st) == 0)
> > > > > + return 1;
> > > > > +
> > > > > + return 0;
> > > > > +}
> > > > > +
> > > > > +/*
> > > > > ?? * Return the CPU id as a raw string.
> > > > > ?? *
> > > > > ?? * Each architecture should provide a more precise id string that
> > > > > @@ -641,7 +669,7 @@ static void pmu_add_cpu_aliases(struct list_head
> > > > > *head, struct perf_pmu *pmu)
> > > > > ?? break;
> > > > > ?? }
> > > > >
> > > > > - if (pmu->is_uncore) {
> > > > > + if (!is_pmu_core(name)) {
> > > > > ?? /* check for uncore devices */
> > > > > ?? if (pe->pmu == NULL)
> > > > > ?? continue;
next prev parent reply other threads:[~2017-12-06 13:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:32 [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-10-16 18:32 ` [PATCH v9 1/5] perf utils: passing pmu as a parameter to function get_cpuid_str Ganapatrao Kulkarni
2017-10-16 18:32 ` [PATCH v9 2/5] perf tools arm64: Add support for get_cpuid_str function Ganapatrao Kulkarni
2017-10-16 18:32 ` [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices Ganapatrao Kulkarni
2017-12-05 2:12 ` Jin, Yao
2017-12-05 7:12 ` Ganapatrao Kulkarni
2017-12-05 7:23 ` Jin, Yao
2017-12-05 12:35 ` Jin, Yao
2017-12-05 13:56 ` Arnaldo Carvalho de Melo
2017-12-05 14:02 ` Ganapatrao Kulkarni
2017-12-05 18:42 ` Arnaldo Carvalho de Melo
2017-12-06 0:30 ` Jin, Yao
2017-12-06 13:47 ` Arnaldo Carvalho de Melo [this message]
2017-12-07 0:49 ` Jin, Yao
2017-12-05 13:58 ` Arnaldo Carvalho de Melo
2017-10-16 18:32 ` [PATCH v9 4/5] perf vendor events arm64: Add ThunderX2 implementation defined pmu core events Ganapatrao Kulkarni
2017-10-16 18:32 ` [PATCH v9 5/5] perf utils: add check for valid cpuid in function perf_pmu__find_map Ganapatrao Kulkarni
2017-10-18 17:49 ` [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-11-06 9:01 ` John Garry
2017-11-07 1:23 ` Will Deacon
2017-11-27 10:04 ` John Garry
2017-12-04 4:41 ` Ganapatrao Kulkarni
2017-12-04 15:09 ` Arnaldo Carvalho de Melo
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=20171206134702.GA12234@kernel.org \
--to=acme@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).