From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
mingo@elte.hu, Robert Richter <robert.richter@amd.com>,
Vince Weaver <vweaver1@eecs.utk.edu>
Subject: Re: [BUG] perf_event: semantic of PERF_SAMPLE_READ unclear
Date: Thu, 25 Aug 2011 19:32:40 +0200 [thread overview]
Message-ID: <1314293560.27911.38.camel@twins> (raw)
In-Reply-To: <CABPqkBS_Og3Vbe90xwyzA8S5ftfF08gMtJdtpqQTHFOwm+CAkg@mail.gmail.com>
On Thu, 2011-08-25 at 19:19 +0200, Stephane Eranian wrote:
> But the difficulty is that
> we cannot grab any locks, not sure we need one given the call path.
Nah we should be able to simply iterate all siblings and update them
in-place, since its group members they should all be co-scheduled. The
only difficulty is cross pmu group members..
next prev parent reply other threads:[~2011-08-25 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 17:19 [BUG] perf_event: semantic of PERF_SAMPLE_READ unclear Stephane Eranian
2011-08-25 17:32 ` Peter Zijlstra [this message]
2011-08-25 21:24 ` Stephane Eranian
2011-08-26 12:02 ` Stephane Eranian
2011-08-26 12:08 ` Stephane Eranian
2011-08-26 12:13 ` Peter Zijlstra
2011-08-26 14:02 ` 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=1314293560.27911.38.camel@twins \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.