From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephane Eranian <eranian@google.com>
Cc: Vince Weaver <vweaver1@eecs.utk.edu>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, mingo@elte.hu
Subject: Re: [tip:perf/urgent] perf/x86: Enable raw event access to Intel offcore events
Date: Mon, 21 Nov 2011 22:48:04 +0100 [thread overview]
Message-ID: <1321912084.28118.38.camel@twins> (raw)
In-Reply-To: <CABPqkBQwvWiaMfAiKAea9WJwJF6ZTwN9e16=VFLQ_cQsfY_FHQ@mail.gmail.com>
On Mon, 2011-11-21 at 22:45 +0100, Stephane Eranian wrote:
> On Mon, Nov 21, 2011 at 10:42 PM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > On Mon, 2011-11-21 at 22:39 +0100, Stephane Eranian wrote:
> >> To solve this problem (in the general case), you need to know which
> >> counter is taken (or required)
> >> by ALL pinned system-wide events across all CPUs. Once you've
> >> constructed the bitmap, you can
> >> use it as the basis (used_mask) to try and schedule the group events.
> >>
> > Its worse, you also need to consider all task-pinned events if you want
> > to be complete. That's an even worse problem.
> >
> But that you know because by the time you do the simulation you already
> know the task the events are attached to. You can get to the list of events
> already attached to the task. Again this is a best effort, it could well be
> that someone else attaches pinned task events just after the simulation.
In the PAPI case yes, but what if you want to create a CPU-wide group,
then you need to consider all task-pinned events that could possibly
land on your CPU. Not fun.
next prev parent reply other threads:[~2011-11-21 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 16:05 [perf] enable raw OFFCORE_EVENTS for non-perf userspace Vince Weaver
2011-08-03 17:00 ` Vince Weaver
2011-08-04 15:55 ` Peter Zijlstra
2011-08-05 2:24 ` Vince Weaver
2011-08-05 9:49 ` Ingo Molnar
2011-11-07 18:30 ` Vince Weaver
2011-11-18 23:34 ` [tip:perf/urgent] perf/x86: Enable raw event access to Intel offcore events tip-bot for Peter Zijlstra
2011-11-21 18:24 ` Vince Weaver
2011-11-21 18:52 ` Peter Zijlstra
2011-11-21 19:01 ` Vince Weaver
2011-11-21 19:04 ` Stephane Eranian
2011-11-21 21:04 ` Vince Weaver
2011-11-21 21:39 ` Stephane Eranian
2011-11-21 21:42 ` Peter Zijlstra
2011-11-21 21:45 ` Stephane Eranian
2011-11-21 21:48 ` Peter Zijlstra [this message]
2011-11-21 22:05 ` Peter Zijlstra
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=1321912084.28118.38.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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