From: Stephane Eranian <eranian@google.com>
To: Peter Zijlstra <peterz@infradead.org>
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, 1 Feb 2010 18:23:29 +0100 [thread overview]
Message-ID: <bd4cb8901002010923q79fa82f5s90a8430b4c037a19@mail.gmail.com> (raw)
In-Reply-To: <1265042731.24455.232.camel@laptop>
On Mon, Feb 1, 2010 at 5:45 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2010-02-01 at 17:14 +0100, Stephane Eranian wrote:
>
>> Using perfmon on Core 2 on a 10s noploop:
>>
>> pfmon -eunhalted_reference_cycles,unhalted_core_cycles,cpu_clk_unhalted:bus
>> noploop 10
>> noploop for 10 seconds
>> 23869090125 UNHALTED_REFERENCE_CYCLES
>> 23849336873 UNHALTED_CORE_CYCLES
>> 2652122099 CPU_CLK_UNHALTED:BUS
>
> Weird, I used:
>
> while :; do :; done &
> while :; do :; done &
> while :; do :; done &
> while :; do :; done &
> perf stat -a -e r013c -e r013c sleep 4
> killall bash
>
> Which gives:
>
> Performance counter stats for 'sleep 4':
>
> 244235699509090 raw 0x13c
> 244235695558036 raw 0x13c
>
Strange. I am running mine on a Q6600.
What's yours?
> 4.005485333 seconds time elapsed
>
> And verified it used fixed counter 2 and general purpose counter 0 using
> sysrq-p.
>
> [523417.108402] CPU#0: gen-PMC0 ctrl: 000000000053013c
> [523417.108403] CPU#0: gen-PMC0 count: 000000ff80019948
> [523417.108405] CPU#0: gen-PMC0 left: 000000007fffffff
> [523417.108407] CPU#0: gen-PMC1 ctrl: 0000000000000000
> [523417.108409] CPU#0: gen-PMC1 count: 0000000000000000
> [523417.108411] CPU#0: gen-PMC1 left: 000000007fffb8a8
> [523417.108412] CPU#0: fixed-PMC0 count: 0000000000000000
> [523417.108414] CPU#0: fixed-PMC1 count: 0000000000000000
> [523417.108416] CPU#0: fixed-PMC2 count: 0000010db1db2117
>
> Using -linus, since that doesn't have any of the recent constraint
> patches in that would avoid us from using fixed-PMC2.
>
>
--
Stephane Eranian | EMEA Software Engineering
Google France | 38 avenue de l'Opéra | 75002 Paris
Tel : +33 (0) 1 42 68 53 00
This email may be confidential or privileged. If you received this
communication by mistake, please
don't forward it to anyone else, please erase all copies and
attachments, and please let me know that
it went to the wrong person. Thanks
next prev parent reply other threads:[~2010-02-01 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 12:50 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 [this message]
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
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=bd4cb8901002010923q79fa82f5s90a8430b4c037a19@mail.gmail.com \
--to=eranian@google.com \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.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=peterz@infradead.org \
--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®