From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org,
davem@davemloft.net, fweisbec@gmail.com, robert.richter@amd.com,
perfmon2-devel@lists.sf.net, eranian@gmail.com
Subject: Re: [PATCH] perf_events: AMD event scheduling (v3)
Date: Wed, 10 Feb 2010 14:17:10 +0100 [thread overview]
Message-ID: <1265807830.11509.295.camel@laptop> (raw)
In-Reply-To: <bd4cb8901002100504i8e716e8ob845f692e031726f@mail.gmail.com>
On Wed, 2010-02-10 at 14:04 +0100, Stephane Eranian wrote:
> > @@ -2268,7 +2268,7 @@ static inline int amd_is_nb_event(struct
> > u64 val = hwc->config & K7_EVNTSEL_EVENT_MASK;
> > /* event code : bits [35-32] | [7-0] */
> > val = (val >> 24) | (val & 0xff);
> > - return val >= 0x0e0;
> > + return val >= 0xe00;
> > }
> >
> I don't understand the change from 0xe0 to 0xe00.
> That's not the same thing at all.
> Event select is bits 0-7 + 32-35.
OK that appears to be my bad, because you extended K7_EVNTSEL_EVENT_MASK
with bit 35 I thought NB events all had bit 35 set.
But looking at the AMD docs it does indeed appear to start at 0xe0, and
there are no events with bit 35 set, only a few with bit 32.
I'll switch it back to 0xe0.
next prev parent reply other threads:[~2010-02-10 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 15:17 Stephane Eranian
2010-02-10 11:59 ` Peter Zijlstra
2010-02-10 13:04 ` Stephane Eranian
2010-02-10 13:17 ` Peter Zijlstra [this message]
2010-02-10 13:28 ` Peter Zijlstra
2010-02-10 13:58 ` stephane eranian
2010-02-10 15:59 ` [perfmon2] " Drongowski, Paul
2010-02-10 16:07 ` Stephane Eranian
2010-02-10 16:17 ` Peter Zijlstra
2010-02-10 16:09 ` Robert Richter
2010-02-10 16:14 ` Peter Zijlstra
2010-02-26 10:25 ` [tip:perf/core] perf_events, x86: AMD event scheduling tip-bot for Stephane Eranian
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=1265807830.11509.295.camel@laptop \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=robert.richter@amd.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
all inboxes | Powered by JetHome®