From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lin Ming <ming.m.lin@intel.com>
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: Wed, 05 Jan 2011 10:50:53 +0100 [thread overview]
Message-ID: <1294221053.2016.206.camel@laptop> (raw)
In-Reply-To: <1293464397.2695.109.camel@localhost>
On Mon, 2010-12-27 at 23:39 +0800, Lin Ming wrote:
> +/* Bits(0-1) {L1, L2, L3, RAM} or {unknown, IO, uncached} */
> +#define LD_LAT_L1 0x00
> +#define LD_LAT_L2 0x01
> +#define LD_LAT_L3 0x02
> +#define LD_LAT_RAM 0x03
> +#define LD_LAT_UNKNOWN 0x00
> +#define LD_LAT_IO 0x01
> +#define LD_LAT_UNCACHED 0x02
> +
> +/* Bits(2-3) {not-used, snoop, local, remote} */
> +#define LD_LAT_NOT_USED (0x00 << 2)
> +#define LD_LAT_SNOOP (0x01 << 2)
> +#define LD_LAT_LOCAL (0x02 << 2)
> +#define LD_LAT_REMOTE (0x03 << 2)
> +
> +/* Bits(4-5) {modified, exclusive, shared, invalid} */
> +#define LD_LAT_MODIFIED (0x00 << 4)
> +#define LD_LAT_EXCLUSIVE (0x01 << 4)
> +#define LD_LAT_SHARED (0x02 << 4)
> +#define LD_LAT_INVALID (0x03 << 4)
> +
> +#define LD_LAT_RESERVED 0x3F
Also, I guess we need to go actually look at the POWER, IA64 and other
PMU docs to see if this sufficiently covers their data-source
capabilities.
Stephane, do you know of more PMUs with data-source capabilities we need
to include in the audit, and do you happen to have all their docs
readily available or do I need to ask google?
prev parent reply other threads:[~2011-01-05 9:50 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
2011-01-05 7:12 ` Lin Ming
2011-01-05 9:50 ` Peter Zijlstra [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=1294221053.2016.206.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox