From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 7/7] perf: Add load latency monitoring on Intel Nehalem/Westmere v2
Date: Thu, 06 Jan 2011 15:49:15 +0800 [thread overview]
Message-ID: <1294300155.9261.62.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1294149804.2016.142.camel@laptop>
On Tue, 2011-01-04 at 22:03 +0800, Peter Zijlstra wrote:
> On Tue, 2011-01-04 at 12:59 +0100, Peter Zijlstra wrote:
> >
> > Right, so I think I want this in 3 patches, one adding the load-latency
> > extra reg thing and PERF_SAMPLE_ADDR usage, one adding
> > PERF_SAMPLE_LATENCY and one adding PERF_SAMPLE_EXTRA, I really dislike
> > the LATENCY_DATA name since that ties the extra data to the latency
> > thing, which isn't at all true for other platforms.
>
> Also, this wants a 4th patch to be fully mergable, we want to have
> tools/perf/ support for these things..
I am thinking what can be added to perf tools....
Seems the average load latency values for each data source and data
linear address is useful.
We may add these support to perf stat or perf record/report.
Any other idea?
data source average load latency(cycles)
========= =============================
Unknown L3 xxx
L1-local xxx
L2-snoop xxx
....
....
L3-miss,remote,exclusive xxx
IO xxx
Uncached memory xxx
data linear address avergage load latency(cycles)
=================== =============================
xxxxxxx xxx
xxxxxxx xxx
xxxxxxx xxx
....
....
Thanks,
Lin Ming
next prev parent reply other threads:[~2011-01-06 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 15:39 [PATCH 7/7] perf: Add load latency monitoring on Intel Nehalem/Westmere v2 Lin Ming
2011-01-04 11:59 ` Peter Zijlstra
2011-01-04 14:03 ` Peter Zijlstra
2011-01-06 7:49 ` Lin Ming [this message]
2011-01-05 7:12 ` Lin Ming
2011-01-05 9:50 ` Peter Zijlstra
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=1294300155.9261.62.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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