From: Will Deacon <will.deacon@arm.com>
To: a.p.zijlstra@chello.nl
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: perf event group siblings not counting in mainline
Date: Sat, 24 Dec 2011 12:54:16 +0000 [thread overview]
Message-ID: <20111224125415.GA14559@mudshark.cambridge.arm.com> (raw)
Hi Peter,
If I try using perf with event groups on a mainline kernel, only the group
leader counts:
linaro@mashed-potato:~$ perf stat --no-scale -g -e task-clock -e cpu-clock -e cs -- ls
hwb linux
Performance counter stats for 'ls':
17.545541 task-clock # 0.634 CPUs utilized
0.000000 cpu-clock
0 cs # 0.000 M/sec
0.027684984 seconds time elapsed
This is fixed by b79387ef ("perf: Fix enable_on_exec for sibling events")
in -next (20111222) but I can't see this queued anywhere for 3.2 (I thought
I might see it in -rc7).
Is this going in for the final cut, or will groups just be borked until 3.3?
Cheers,
Will
next reply other threads:[~2011-12-24 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 12:54 Will Deacon [this message]
2012-01-10 11:09 ` perf event group siblings not counting in mainline Will Deacon
2012-01-10 11:16 ` Peter Zijlstra
2012-01-10 11:56 ` Will Deacon
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=20111224125415.GA14559@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).