[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200117230356.GA2093716@kroah.com>
Date: Sat, 18 Jan 2020 00:03:56 +0100
From: Greg KH <gregkh@...ux-foundation.org>
To: Andi Kleen <ak@...ux.intel.com>
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
On Fri, Jan 17, 2020 at 11:12:20AM -0800, Andi Kleen wrote:
> > > pmon0-3: list of pci busses indexed by die
> > >
> > > To be honest the approach doesn't seem unreasonable to me. It's similar
> > > e.g. how we express lists of cpus or nodes in sysfs today.
>
> <snipped repeated form letter non answer to question>
>
> 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 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?
greg k-h
Powered by blists - more mailing lists