From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Lin Ming <ming.m.lin@intel.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Carl Love <cel@linux.ibm.com>
Subject: Re: [RFC PATCH 3/3 v3] perf: Update perf tool to monitor uncore events
Date: Tue, 14 Dec 2010 15:13:14 +0100 [thread overview]
Message-ID: <20101214141314.GC21257@basil.fritz.box> (raw)
In-Reply-To: <1292330007.6803.1629.camel@twins>
On Tue, Dec 14, 2010 at 01:33:27PM +0100, Peter Zijlstra wrote:
> > > First of all, "uncore" is an x86-specific term and so it's not clear to
> > > me if you meant for all arches to utilize this encoding for all "not
> > > core but on the same die" events (IBM Power arch refers to this as
> > > "nest" logic).
>
> I don't think the x86 uncore matches the "not on core but on the same
> die" definition. The x86-uncore thing is more like a memory controller
> PMU (and since the memory controller is on die it is of course on die,
memory controller + interconnect + cache + power management + various other things.
Older x86 CPUs also had special PMUs on die for parts of that, but
without memory controller.
> but its not just any random on-die thing).
>
> The wire-speed thing has tons of special purpose 'cores' on die, each of
> them having a PMU.
Modern x86 CPUs also have other PMUs, at least in package (e.g. in the
GPU)
> Using the sysfs stuff you could actually expose each individually.
I expect this will be also needed on x86. Also there are x86 SOCs
where other parts of the SOC will have their own counters too.
So in general a flexible scheme to describe that is useful.
-Andi
next prev parent reply other threads:[~2010-12-14 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 5:20 [RFC PATCH 3/3 v3] perf: Update perf tool to monitor uncore events Lin Ming
2010-12-14 1:28 ` Corey Ashford
2010-12-14 2:15 ` Lin Ming
2010-12-14 12:33 ` Peter Zijlstra
2010-12-14 14:13 ` Andi Kleen [this message]
2010-12-15 17:14 ` Martin Hicks
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=20101214141314.GC21257@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=cel@linux.ibm.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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.