public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Don Zickus <dzickus@redhat.com>
Cc: Joe Mario <jmario@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	eranian@google.com, Arnaldo Carvalho de Melo <acme@kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	jolsa@redhat.com, rfowles@redhat.com
Subject: Re: perf:  Translating mmap2 ids into socket info?
Date: Thu, 23 Oct 2014 13:01:25 +0200	[thread overview]
Message-ID: <20141023110125.GO21513@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141022203834.GL135937@redhat.com>

On Wed, Oct 22, 2014 at 04:38:34PM -0400, Don Zickus wrote:
> On Wed, Oct 22, 2014 at 10:02:19PM +0200, Peter Zijlstra wrote:

> > Or if you'd used more counters that track the node interconnect traffic
> > ;-) There are a few simple ones that count local/remote type things
> > (offcore), but using the uncore counters you can track way more.
> 
> Ha!  I have been telling myself for a year I would try to learn more about
> those offcore/uncore counters.  Is there documentation for how to access
> the uncore stuff?  Do I have to long hand it with 'perf record -e
> uncore_qpi_1/<stuff>/ foo'?

So uncore is something unholy complicated and different for each cpu,
although the newer chips seems to have limited the variation somewhat.

I would suggest you start with the offcore bits, those are in the SDM.

We have some numa cache events, but if those don't work for you you
might want to look at the offcore code we have in the kernel to help
construct your own events.

I Cc'ed you on a patch series cleaning up some of the recent HSW code.

  reply	other threads:[~2014-10-23 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 16:20 perf: Translating mmap2 ids into socket info? Don Zickus
2014-10-22 16:45 ` Peter Zijlstra
2014-10-22 17:42   ` Arnaldo Carvalho de Melo
2014-10-22 18:15     ` Arnaldo Carvalho de Melo
2014-10-22 19:55       ` Peter Zijlstra
2014-10-22 19:54     ` Peter Zijlstra
2014-10-22 18:09   ` Joe Mario
2014-10-22 20:02     ` Peter Zijlstra
2014-10-22 20:38       ` Don Zickus
2014-10-23 11:01         ` Peter Zijlstra [this message]
2014-10-23 11:30         ` Peter Zijlstra
2014-10-23 13:10           ` Don Zickus

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=20141023110125.GO21513@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dzickus@redhat.com \
    --cc=eranian@google.com \
    --cc=jmario@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rfowles@redhat.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