From: Greg KH <gregkh@linux-foundation.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: roman.sudarikov@linux.intel.com, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, bgregg@netflix.com,
kan.liang@linux.intel.com, alexander.antonov@intel.com
Subject: Re: [PATCH v4 2/2] perf x86: Exposing an Uncore unit to PMON for Intel Xeon® server platform
Date: Sat, 18 Jan 2020 00:03:56 +0100 [thread overview]
Message-ID: <20200117230356.GA2093716@kroah.com> (raw)
In-Reply-To: <20200117191220.GN302770@tassilo.jf.intel.com>
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
next prev parent reply other threads:[~2020-01-17 23:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 13:37 [PATCH v4 0/2] perf x86: Exposing IO stack to IO PMON mapping through sysfs roman.sudarikov
2020-01-17 13:37 ` [PATCH v4 1/2] perf x86: Infrastructure for exposing an Uncore unit to PMON mapping roman.sudarikov
2020-01-17 14:16 ` Greg KH
2020-01-17 13:37 ` [PATCH v4 2/2] perf x86: Exposing an Uncore unit to PMON for Intel Xeon® server platform roman.sudarikov
2020-01-17 14:19 ` Greg KH
2020-01-17 16:23 ` Andi Kleen
2020-01-17 16:54 ` Greg KH
2020-01-17 17:27 ` Andi Kleen
2020-01-17 18:42 ` Greg KH
2020-01-17 19:12 ` Andi Kleen
2020-01-17 23:03 ` Greg KH [this message]
2020-01-17 23:21 ` Andi Kleen
2020-01-21 16:15 ` Sudarikov, Roman
2020-01-21 17:15 ` Greg KH
2020-01-28 14:55 ` Sudarikov, Roman
2020-01-28 20:19 ` Liang, Kan
2020-01-17 14:14 ` [PATCH v4 0/2] perf x86: Exposing IO stack to IO PMON mapping through sysfs Greg KH
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=20200117230356.GA2093716@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgregg@netflix.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=roman.sudarikov@linux.intel.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 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).