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,
Arjan van de Ven <arjan@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] perf_events: fix bug in hw_perf_enable()
Date: Mon, 01 Feb 2010 19:20:22 +0100 [thread overview]
Message-ID: <1265048422.24455.236.camel@laptop> (raw)
In-Reply-To: <bd4cb8901002010956p70242197x7bc4569e91265da2@mail.gmail.com>
On Mon, 2010-02-01 at 18:56 +0100, Stephane Eranian wrote:
> On Mon, Feb 1, 2010 at 6:46 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Mon, 2010-02-01 at 18:23 +0100, Stephane Eranian wrote:
> >> > 244235699509090 raw 0x13c
> >> > 244235695558036 raw 0x13c
> >> >
> >> Strange. I am running mine on a Q6600.
> >> What's yours?
> >
> > These numbers came from a T9400, but my Q9450 does something similar.
> >
> Are you sure you are reading from the correct corresponding data registers?
It sure got me wondering, I'll go over that fixed counter code in
arch/x86/kernel/cpu/perf_event.c in the morning.
next prev parent reply other threads:[~2010-02-01 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 12:50 [PATCH] perf_events: fix bug in hw_perf_enable() Stephane Eranian
2010-02-01 15:35 ` Peter Zijlstra
2010-02-01 16:04 ` Peter Zijlstra
2010-02-01 16:14 ` Stephane Eranian
2010-02-01 16:45 ` Peter Zijlstra
2010-02-01 17:23 ` Stephane Eranian
2010-02-01 17:46 ` Peter Zijlstra
2010-02-01 17:56 ` Stephane Eranian
2010-02-01 18:20 ` Peter Zijlstra [this message]
2010-02-01 16:12 ` Stephane Eranian
2010-02-01 16:47 ` Peter Zijlstra
2010-02-01 17:22 ` Stephane Eranian
2010-02-04 9:57 ` [tip:perf/core] perf_events, x86: Fix " 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=1265048422.24455.236.camel@laptop \
--to=peterz@infradead.org \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.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