From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: eranian@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Robert Richter <robert.richter@amd.com>,
Paul Mackerras <paulus@samba.org>,
Andi Kleen <andi@firstfloor.org>,
Maynard Johnson <mpjohn@us.ibm.com>, Carl Love <cel@us.ibm.com>,
Corey J Ashford <cjashfor@us.ibm.com>,
Philip Mucci <mucci@eecs.utk.edu>,
Dan Terpstra <terpstra@eecs.utk.edu>,
perfmon2-devel <perfmon2-devel@lists.sourceforge.net>
Subject: Re: perf_counters issue with PERF_SAMPLE_GROUP
Date: Tue, 11 Aug 2009 18:05:44 +0200 [thread overview]
Message-ID: <1250006744.10001.29.camel@twins> (raw)
In-Reply-To: <7c86c4470908110841wca07382gf7487c0ed55909f2@mail.gmail.com>
On Tue, 2009-08-11 at 17:41 +0200, stephane eranian wrote:
> Hi,
>
> It seems to me there is a problem with the group counter values
> when you use PERF_SAMPLE_GROUP. The counts are bogus
> for all events.
>
> Test case is pretty simple:
> - single group, 2 events
> - sampling on PERF_COUNT_HW_CYCLES
> - other event is PERF_COUNT_HW_CYCLES
> - leader has SAMPLE_IP|SAMPLE_GROUP
> - no inheritance
> - single thread
> - using sampling in one shot mode with PERF_COUNTER_IOC_REFRESH
> - all events but leader start with disabled = 0 (i.e., enabled)
> - sampling period is 240000000 (cycles)
>
> Notification 1: ip=0x401300 39100608 PERF_COUNT_HW_CPU_CYCLES (12)
> Notification 2: ip=0x401300 17991616 PERF_COUNT_HW_CPU_CYCLES (12)
> Notification 3: ip=0x401300 17981248 PERF_COUNT_HW_CPU_CYCLES (12)
> Notification 4: ip=0x401300 9409478912 PERF_COUNT_HW_CPU_CYCLES (12)
>
> I would expect the value for the 2nd event to be close to 240000000.
> But instead,
> it is going up and down. The IP, nr and id (12) fields are correct, so
> the parsing of
> the buffer is correct. This is with the latest from Linus's 2.6.31-rc5.
Could have broken somewhere along the line, the group stuff doesn't get
tested a lot, if at all.
perf used to have some support for it, not sure what the current state
is.
You seem to have forgotten to append your test.c though :-)
> Related to PERF_SAMPLE_GROUP, I believe there is some information missing.
> You need to provide the TIMING information because in the case of SAMPLE_GROUP
> you'd like to be able to scale the values of the counters you are
> collecting. And you
> need the timing at the moment, the sample was recorded not later.
Right, so something like the below, possibly complemented with having
PERF_COUNTER_IOC_RESET also reset the run-times?
---
include/linux/perf_counter.h | 3 +++
kernel/perf_counter.c | 20 ++++++++++++++++++--
2 files changed, 21 insertions(+), 2 deletions(-)
diff --git a/include/linux/perf_counter.h b/include/linux/perf_counter.h
index 2b36afe..44a056b 100644
--- a/include/linux/perf_counter.h
+++ b/include/linux/perf_counter.h
@@ -365,10 +365,13 @@ enum perf_event_type {
* { u64 period; } && PERF_SAMPLE_PERIOD
*
* { u64 nr;
+ * { u64 time_enabled; } && PERF_FORMAT_ENABLED
+ * { u64 time_running; } && PERF_FORMAT_RUNNING
* { u64 id, val; } cnt[nr]; } && PERF_SAMPLE_GROUP
*
* { u64 nr,
* u64 ips[nr]; } && PERF_SAMPLE_CALLCHAIN
+ *
* { u32 size;
* char data[size];}&& PERF_SAMPLE_RAW
* };
diff --git a/kernel/perf_counter.c b/kernel/perf_counter.c
index e26d2fc..e61e701 100644
--- a/kernel/perf_counter.c
+++ b/kernel/perf_counter.c
@@ -2636,6 +2636,7 @@ void perf_counter_output(struct perf_counter *counter, int nmi,
{
int ret;
u64 sample_type = counter->attr.sample_type;
+ u64 read_format = counter->attr.read_format;
struct perf_output_handle handle;
struct perf_event_header header;
u64 ip;
@@ -2703,6 +2704,10 @@ void perf_counter_output(struct perf_counter *counter, int nmi,
if (sample_type & PERF_SAMPLE_GROUP) {
header.size += sizeof(u64) +
counter->nr_siblings * sizeof(group_entry);
+ if (read_format & PERF_FORMAT_ENABLED)
+ header.size += sizeof(u64);
+ if (read_format & PERF_FORMAT_RUNNING)
+ header.size += sizeof(u64);
}
if (sample_type & PERF_SAMPLE_CALLCHAIN) {
@@ -2765,9 +2770,20 @@ void perf_counter_output(struct perf_counter *counter, int nmi,
*/
if (sample_type & PERF_SAMPLE_GROUP) {
struct perf_counter *leader, *sub;
- u64 nr = counter->nr_siblings;
+ u64 val;
+
+ val = counter->nr_siblings;
+ perf_output_put(&handle, val);
- perf_output_put(&handle, nr);
+ if (read_format & PERF_FORMAT_ENABLED) {
+ val = counter->total_time_enabled;
+ perf_output_put(&handle, val);
+ }
+
+ if (read_format & PERF_FORMAT_RUNNING) {
+ val = counter->total_time_running;
+ perf_output_put(&handle, val);
+ }
leader = counter->group_leader;
list_for_each_entry(sub, &leader->sibling_list, list_entry) {
next prev parent reply other threads:[~2009-08-11 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 15:41 perf_counters issue with PERF_SAMPLE_GROUP stephane eranian
2009-08-11 16:05 ` Peter Zijlstra [this message]
2009-08-11 19:40 ` stephane eranian
2009-08-11 20:55 ` Peter Zijlstra
2009-08-11 21:08 ` stephane eranian
2009-08-12 8:32 ` Peter Zijlstra
2009-08-12 9:02 ` Ingo Molnar
2009-08-12 12:22 ` stephane eranian
2009-08-13 9:46 ` Ingo Molnar
2009-08-13 19:15 ` stephane eranian
2009-08-13 23:13 ` Corey Ashford
2009-08-13 23:49 ` Paul Mackerras
2009-08-12 20:54 ` 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=1250006744.10001.29.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cel@us.ibm.com \
--cc=cjashfor@us.ibm.com \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpjohn@us.ibm.com \
--cc=mucci@eecs.utk.edu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sourceforge.net \
--cc=robert.richter@amd.com \
--cc=terpstra@eecs.utk.edu \
--cc=tglx@linutronix.de \
/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