lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230526102428.00002b6a@Huawei.com>
Date:   Fri, 26 May 2023 10:24:28 +0100
From:   Jonathan Cameron <Jonathan.Cameron@...wei.com>
To:     Stephane Eranian <eranian@...gle.com>
CC:     Namhyung Kim <namhyung@...il.com>,
        Liang Kan <kan.liang@...ux.intel.com>,
        <linux-cxl@...r.kernel.org>, <peterz@...radead.org>,
        <mark.rutland@....com>, <will@...nel.org>, <mingo@...hat.com>,
        <acme@...nel.org>, <dan.j.williams@...el.com>,
        <linuxarm@...wei.com>, <linux-perf-users@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        Davidlohr Bueso <dave@...olabs.net>,
        "Dave Jiang" <dave.jiang@...el.com>
Subject: Re: [PATCH v6 4/5] perf: CXL Performance Monitoring Unit driver

On Thu, 25 May 2023 18:18:55 -0700
Stephane Eranian <eranian@...gle.com> wrote:

> On Thu, May 25, 2023 at 6:06 PM Namhyung Kim <namhyung@...il.com> wrote:
> >
> > Add Stephane to CC.
> >
> > On Thu, Apr 13, 2023 at 7:35 AM Jonathan Cameron
> > <Jonathan.Cameron@...wei.com> wrote:  
> > >
> > > CXL rev 3.0 introduces a standard performance monitoring hardware
> > > block to CXL. Instances are discovered using CXL Register Locator DVSEC
> > > entries. Each CXL component may have multiple PMUs.
> > >
> > > This initial driver supports a subset of types of counter.
> > > It supports counters that are either fixed or configurable, but requires
> > > that they support the ability to freeze and write value whilst frozen.
> > >
> > > Development done with QEMU model which will be posted shortly.
> > >
> > > Example:
> > >
> > > $ perf stat -e cxl_pmu_mem0.0/h2d_req_snpcur/ -e cpmu0/h2d_req_snpdata/ -e cpmu0/clock_ticks/ sleep 1
> > >
> > > Performance counter stats for 'system wide':
> > >  
> 
> Unless I am mistaken, I don't think this output corresponds to the
> cmdline above. I think the -a is missing.
> I don't think you can measure CXL traffic per-thread. Please confirm.
> Thanks.

It doesn't seem to make any difference whether I include -a or not and
the perf man page says 

       -a, --all-cpus
           system-wide collection from all CPUs (default if no target is
           specified)

However I'm not sure what target means in this case as there is no
mention of it anywhere else in the perf-stat man page.  My guess is thread
or process provided by -p or -t.  So default applies in the above command line.
Doesn't hurt to be more explicit though, so I've added -a.

The command line is wrong however as I failed to update the device name
for the 2nd and 3rd events.


> 
> >  
> > > 96,757,023,244,321      cxl_pmu_mem0.0/h2d_req_snpcur/
> > > 96,757,023,244,365      cxl_pmu_mem0.0/h2d_req_snpdata/
> > > 193,514,046,488,653      cxl_pmu_mem0.0/clock_ticks/
> > >
> > >        1.090539600 seconds time elapsed

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ