From: Namhyung Kim <namhyung.kim@lge.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
arnaldo.melo@gmail.com,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/8] Annotation weekly ponies delivery
Date: Thu, 17 May 2012 09:13:18 +0900 [thread overview]
Message-ID: <87y5or1x7l.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <87liksd5wi.fsf@sejong.aot.lge.com> (Namhyung Kim's message of "Wed, 16 May 2012 14:57:49 +0900")
Hi,
On Wed, 16 May 2012 14:57:49 +0900, Namhyung Kim wrote:
> In fact, my perf stat -g was already broken - it cannot count at
> all on my SNB box. I'll investigate it more.
>
It's like a matter of the number of the hw counters. The perf stat -g
uses 6 hw events, but I can use up to 5 hw events on my SNB machine:
$ ./perf stat -g -e cycles,cache-references,cache-misses,instructions,branches sleep 1
Performance counter stats for 'sleep 1':
999,008 cycles # 0.000 GHz
10,963 cache-references
2,630 cache-misses # 23.990 % of all cache refs
635,225 instructions # 0.64 insns per cycle
128,014 branches
1.001466421 seconds time elapsed
But I adding branch-misses event outputs:
Performance counter stats for 'sleep 1':
<not counted> cycles
<not counted> cache-references
<not counted> cache-misses
<not counted> instructions
<not counted> branches
<not counted> branch-misses
1.000742533 seconds time elapsed
However adding ref-cycles is fine (Is it related to fixed counters?):
Performance counter stats for 'sleep 1':
1,027,263 cycles # 0.000 GHz
12,435 cache-references
2,747 cache-misses # 22.091 % of all cache refs
650,100 instructions # 0.63 insns per cycle
130,765 branches
2,367,488 ref-cycles
1.001557088 seconds time elapsed
BTW, dmesg says I have 7, but a counter was taken by NMI watchdog:
$ dmesg | grep -A32 Performance
[ 0.137227] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
[ 0.137232] ... version: 3
[ 0.137233] ... bit width: 48
[ 0.137234] ... generic registers: 4
[ 0.137235] ... value mask: 0000ffffffffffff
[ 0.137236] ... max period: 000000007fffffff
[ 0.137237] ... fixed-purpose events: 3
[ 0.137238] ... event mask: 000000070000000f
[ 0.143371] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.149251] Booting Node 0, Processors #1
[ 0.162396] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.166265] #2
[ 0.179401] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.183263] #3
[ 0.196399] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.200263] #4
[ 0.213398] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.217268] #5
[ 0.230404] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.234263] #6
[ 0.247402] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.251268] #7
[ 0.264405] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.268266] #8
[ 0.281403] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.285268] #9
[ 0.298405] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.302264] #10
[ 0.315401] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.319266] #11 Ok.
[ 0.332404] NMI watchdog: enabled, takes one hw-pmu counter.
[ 0.332435] Brought up 12 CPUs
[ 0.332437] Total of 12 processors activated (76799.44 BogoMIPS).
Thanks,
Namhyung
prev parent reply other threads:[~2012-05-17 0:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 19:52 Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 1/8] perf annotate: Use raw form for register indirect call instructions Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 2/8] perf annotate: Resolve symbols using objdump comment Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 3/8] perf annotate: Resolve symbols using objdump comment for single op ins Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 4/8] perf annotate: Augment lock instruction output Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 5/8] perf annotate: Introduce ->free() method in ins_ops Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 6/8] perf annotate browser: Count the numbers of jump sources to a target Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 7/8] perf annotate browser: Show 'jumpy' functions Arnaldo Carvalho de Melo
2012-05-12 19:53 ` [PATCH 8/8] perf annotate browser: Add key bindings help window Arnaldo Carvalho de Melo
2012-05-12 20:40 ` [GIT PULL 0/8] Annotation weekly ponies delivery Linus Torvalds
2012-05-12 21:25 ` Arnaldo Carvalho de Melo
2012-05-12 22:29 ` Linus Torvalds
2012-05-14 7:05 ` Ingo Molnar
2012-05-14 11:13 ` Peter Zijlstra
2012-05-14 11:55 ` Ingo Molnar
2012-05-14 15:06 ` Namhyung Kim
2012-05-15 4:48 ` Namhyung Kim
2012-05-15 10:32 ` Peter Zijlstra
2012-05-15 14:44 ` Namhyung Kim
2012-05-15 17:07 ` Peter Zijlstra
2012-05-16 5:57 ` Namhyung Kim
2012-05-16 8:19 ` Namhyung Kim
2012-05-17 0:13 ` Namhyung Kim [this message]
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=87y5or1x7l.fsf@sejong.aot.lge.com \
--to=namhyung.kim@lge.com \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=arjan@infradead.org \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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®