[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200117232154.GP302770@tassilo.jf.intel.com>
Date: Fri, 17 Jan 2020 15:21:54 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Greg KH <gregkh@...ux-foundation.org>
Cc: roman.sudarikov@...ux.intel.com, peterz@...radead.org,
mingo@...hat.com, acme@...nel.org, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
namhyung@...nel.org, linux-kernel@...r.kernel.org,
eranian@...gle.com, bgregg@...flix.com, kan.liang@...ux.intel.com,
alexander.antonov@...el.com
Subject: Re: [PATCH v4 2/2] perf x86: Exposing an Uncore unit to PMON for Intel Xeon® server platform
> > Roman,
> >
> > I suppose you'll need something like
> >
> > /sys/device/system/dieXXX/pci-pmon<0-3>/bus
> >
> > and bus could be a symlink to the pci bus directory.
>
> Why do you need to link to the pci bus directory?
The goal is to identify which bus is counted by the perfmon
counter. I suppose it could be a field containing the bus
identifier too, but I think symlinks are used elsewhere.
> > The whole thing will be ugly and complicated and slow and difficult
> > to parse, but it will presumably follow Greg's rules.
>
> Who needs to parse this? What tool will do it and for what?
perf parses is to output PCI bandwidth per PCI device.
-Andi
Powered by blists - more mailing lists