From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
ming.m.lin@intel.com
Subject: Re: [rfc 1/3] perf, x86: P4 PMU - describe config format
Date: Fri, 26 Nov 2010 13:59:39 +0100 [thread overview]
Message-ID: <1290776379.2145.143.camel@laptop> (raw)
In-Reply-To: <AANLkTikjEDVmQRt4ZxwwXJznX2X3zSqSY=zoPtuN1omY@mail.gmail.com>
On Fri, 2010-11-26 at 13:48 +0100, Stephane Eranian wrote:
> Reviewed-by: Stephane Eranian <eranian@google.com>
The new one, right? The one that reads:
+ * Low 32 bits
+ * -----------
+ * 0-6: P4_PEBS_METRIC enum
+ * 7-11: reserved
+ * 12: reserved (Enable)
+ * 13-15: reserved (ESCR select)
+ * 16-17: Active Thread
+ * 18: Compare
+ * 19: Complement
+ * 20-23: Threshold
+ * 24: Edge
+ * 25: reserved (FORCE_OVF)
+ * 26: reserved (OVF_PMI_T0)
+ * 27: reserved (OVF_PMI_T1)
+ * 28-29: reserved
+ * 30: reserved (Cascade)
+ * 31: reserved (OVF)
+ *
+ * High 32 bits
+ * ------------
+ * 0: reserved (T1_USR)
+ * 1: reserved (T1_OS)
+ * 2: reserved (T0_USR)
+ * 3: reserved (T0_OS)
+ * 4: Tag Enable
+ * 5-8: Tag Value
+ * 9-24: Event Mask (may use P4_ESCR_EMASK_BIT helper)
+ * 25-30: enum P4_EVENTS
+ * 31: reserved (HT thread)
next prev parent reply other threads:[~2010-11-26 12:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 22:46 [rfc 0/3] perf,x86: p4 pmu series Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 1/3] perf, x86: P4 PMU - describe config format Cyrill Gorcunov
2010-11-26 10:57 ` Stephane Eranian
2010-11-26 11:14 ` Cyrill Gorcunov
2010-11-26 11:32 ` Cyrill Gorcunov
2010-11-26 11:35 ` Stephane Eranian
2010-11-26 11:58 ` Cyrill Gorcunov
2010-11-26 12:46 ` Stephane Eranian
2010-11-26 13:04 ` Cyrill Gorcunov
2010-11-26 13:06 ` Peter Zijlstra
2010-11-26 13:47 ` Cyrill Gorcunov
2010-11-26 13:10 ` Stephane Eranian
2010-11-26 13:50 ` Cyrill Gorcunov
2010-11-26 13:54 ` Stephane Eranian
2010-11-26 15:27 ` Cyrill Gorcunov
2010-11-26 16:22 ` Stephane Eranian
2010-11-26 17:16 ` Cyrill Gorcunov
2010-11-26 18:05 ` Stephane Eranian
2010-11-26 20:11 ` Cyrill Gorcunov
2010-11-26 12:48 ` Stephane Eranian
2010-11-26 12:59 ` Peter Zijlstra [this message]
2010-11-26 13:07 ` Stephane Eranian
2010-11-26 13:07 ` Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 2/3] perf, x86: P4 PMU - Fix unflagged overflows handling v4 Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 3/3] perf, x86: P4 PMU -- export ABI part of event config to userspace Cyrill Gorcunov
2010-11-24 8:32 ` Peter Zijlstra
2010-11-24 8:48 ` Cyrill Gorcunov
2010-11-24 9:02 ` Peter Zijlstra
2010-11-24 9:39 ` Cyrill Gorcunov
2010-11-24 11:46 ` Cyrill Gorcunov
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=1290776379.2145.143.camel@laptop \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=gorcunov@openvz.org \
--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