From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Extending ARM perf-events for multiple PMUs
Date: Mon, 11 Apr 2011 14:47:55 +0200 [thread overview]
Message-ID: <1302526075.2388.97.camel@twins> (raw)
In-Reply-To: <1302521393.24286.66.camel@e102144-lin.cambridge.arm.com>
On Mon, 2011-04-11 at 12:29 +0100, Will Deacon wrote:
> > If you've got system wide things like GPUs, where every cpu maps to the
> > same device, simply use the first online cpu and create a pmu instance
> > per device.
>
> Would this result in userspace attributing all of the data to a
> particular CPU? We could consider allowing events where the cpu is -1
> and the task pid is -1 as well. Non system-wide PMUs could reject these
> and demand multiple events instead.
Not at such, but you need a cpu to receive interrupts on and program the
hardware from etc. Currently most core code assumes things are either
restrained to a single cpu or serialized by virtue of a task never
running on more than 1 cpu at a time.
I'm not quite sure how hard these assumptions are, and we might be able
to get away with making it a little less strict, but that's something
you'd have to play with.
next prev parent reply other threads:[~2011-04-11 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 17:15 [RFC] Extending ARM perf-events for multiple PMUs Will Deacon
2011-04-08 18:10 ` Linus Walleij
2011-04-11 11:12 ` Will Deacon
2011-04-09 11:40 ` Peter Zijlstra
2011-04-11 11:29 ` Will Deacon
2011-04-11 12:47 ` Peter Zijlstra [this message]
2011-04-11 17:44 ` Ashwin Chaugule
2011-04-12 17:45 ` Will Deacon
2011-04-11 18:00 ` Ashwin Chaugule
2011-04-12 7:39 ` Ming Lei
2011-04-12 10:30 ` Peter Zijlstra
2011-04-12 11:12 ` Ming Lei
2011-04-11 17:29 ` Ashwin Chaugule
2011-04-11 18:00 ` Will Deacon
2011-04-11 20:46 ` Ashwin Chaugule
2011-04-12 18:08 ` Will Deacon
2011-04-13 5:09 ` Ashwin Chaugule
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=1302526075.2388.97.camel@twins \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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