From: Andi Kleen <ak@linux.intel.com>
To: Greg KH <gregkh@linux-foundation.org>
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: Fri, 17 Jan 2020 15:21:54 -0800 [thread overview]
Message-ID: <20200117232154.GP302770@tassilo.jf.intel.com> (raw)
In-Reply-To: <20200117230356.GA2093716@kroah.com>
> > 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
next prev parent reply other threads:[~2020-01-17 23:22 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
2020-01-17 23:21 ` Andi Kleen [this message]
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=20200117232154.GP302770@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.antonov@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgregg@netflix.com \
--cc=eranian@google.com \
--cc=gregkh@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.