public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
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 09:10:04 -0400	[thread overview]
Message-ID: <20141023131004.GS135937@redhat.com> (raw)
In-Reply-To: <20141023113001.GA12706@worktop.programming.kicks-ass.net>

On Thu, Oct 23, 2014 at 01:30:01PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 22, 2014 at 04:38:34PM -0400, Don Zickus wrote:
> > 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'?
> 
> For uncore there is some in the SDM and there are these documents; there
> might be more but who knows.
> 
> http://www.intel.com/Assets/PDF/designguide/323535.pdf 
> http://www.intel.com/content/dam/www/public/us/en/documents/design-guides/xeon-e5-2600-uncore-guide.pdf 

Thanks!

Cheers,
Don

      reply	other threads:[~2014-10-23 13:10 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
2014-10-23 11:30         ` Peter Zijlstra
2014-10-23 13:10           ` Don Zickus [this message]

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=20141023131004.GS135937@redhat.com \
    --to=dzickus@redhat.com \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=jmario@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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