[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1294300155.9261.62.camel@minggr.sh.intel.com>
Date: Thu, 06 Jan 2011 15:49:15 +0800
From: Lin Ming <ming.m.lin@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
Stephane Eranian <eranian@...gle.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 7/7] perf: Add load latency monitoring on Intel
Nehalem/Westmere v2
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists