From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: linux-kernel@vger.kernel.org, fbuihuu@gmail.com, mingo@elte.hu,
paulus@samba.org, acme@redhat.com
Subject: Re: perf: regression with PERF_EVENT_IOC_REFRESH
Date: Mon, 23 May 2011 22:22:21 +0200 [thread overview]
Message-ID: <1306182141.2497.5.camel@laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1105231555490.17453@cl320.eecs.utk.edu>
On Mon, 2011-05-23 at 16:04 -0400, Vince Weaver wrote:
> Hello
>
> the changeset 2e939d1d perf: Limit event refresh to sampling event
>
> changes the behavior of
> ioctl( , PERF_EVENT_IOC_REFRESH, )
>
> before the changeset, you could have a counter group where only one of the
> subevents was sampling. PERF_EVENT_IOC_REFRESH would correctly enable
> sampling for only that subevent.
But how? it adds to the event_limit of the event you call the ioctl()
on, not on any of the group siblings.
> With the changeset applied, this fails with EINVALID. Now you can only
> sample in a group leader.
I'm not quite seeing how group-leaders are relevant here, you can only
call this ioctl() on sampling events, regardless of if they're they
group leader or a sibling.
> Was this an intended change? It breaks various of our PAPI regression
> tests that worked fine before the change was committed.
I'm not quite seeing what's wrong yet, the change seemed simple enough
in that calling that ioctl() on an event that wasn't capable of
generating samples doesn't make sense, since it will increase the event
limit for the event you call it on.
next prev parent reply other threads:[~2011-05-23 20:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 20:04 perf: regression with PERF_EVENT_IOC_REFRESH Vince Weaver
2011-05-23 20:22 ` Peter Zijlstra [this message]
2011-05-24 6:20 ` Vince Weaver
2011-05-24 10:30 ` Peter Zijlstra
2011-05-24 15:04 ` Vince Weaver
2011-05-24 15:10 ` Peter Zijlstra
2011-05-24 15:40 ` Ingo Molnar
2011-05-24 20:31 ` Vince Weaver
2011-05-25 10:39 ` Ingo Molnar
2011-05-25 21:24 ` Vince Weaver
2011-05-24 17:53 ` Vince Weaver
2011-05-24 15:11 ` Peter Zijlstra
2011-05-24 15:18 ` Peter Zijlstra
2011-05-24 21:48 ` Vince Weaver
2011-05-28 3:38 ` Vince Weaver
2011-05-28 10:22 ` Peter Zijlstra
2011-05-28 13:26 ` perf: definition of a "regression" Vince Weaver
2011-06-02 7:45 ` Ingo Molnar
2011-05-29 16:54 ` perf: regression with PERF_EVENT_IOC_REFRESH Vince Weaver
2011-05-31 1:33 ` perf: [patch] " Vince Weaver
2011-05-31 7:17 ` Peter Zijlstra
2011-05-31 7:23 ` Peter Zijlstra
2011-05-31 13:49 ` Vince Weaver
2011-05-31 15:52 ` Peter Zijlstra
2011-05-31 16:39 ` Vince Weaver
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=1306182141.2497.5.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fbuihuu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=vweaver1@eecs.utk.edu \
/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