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: fix bug in hw_perf_enable()
Date: Mon, 01 Feb 2010 17:47:17 +0100 [thread overview]
Message-ID: <1265042837.24455.234.camel@laptop> (raw)
In-Reply-To: <bd4cb8901002010812x505b77b4h754f573e3bbfa615@mail.gmail.com>
On Mon, 2010-02-01 at 17:12 +0100, Stephane Eranian wrote:
> > btw, I've also added the below, from what I can make from the docs
> fixed
> > counter 2 is identical to arch perf event 0x013c, as per table A-1
> and
> > A-7. Both are called CPU_CLK_UNHALTED.REF, except for Core2, where
> > 0x013c is called CPU_CLK_UNHALTED.BUS.
> >
>
> If you measure 0x013c in a generic counter or in fixed counter 2
> it will count the same thing but not at the same rate.
> This is true on Core2, Atom, Nehalem, Westmere. The ratio is the
> clock/bus ratio.
But for Nehalem and Westmere event 0x3c umask 0x01 is referred to as
CPU_CLK_UNHALTED.REF_P (Tables A-2 and A-4),
Fixed Counter 2 is referred to as CPU_CLK_UNHALTED.REF (Table A-7).
For Core2 and Atom (Table A-8, A-9) it is called CPU_CLK_UNHALTED.BUS,
for these entries there is talk about a fixed ratio.
next prev parent reply other threads:[~2010-02-01 16:47 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
2010-02-01 16:12 ` Stephane Eranian
2010-02-01 16:47 ` Peter Zijlstra [this message]
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=1265042837.24455.234.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