From: ashwinc@codeaurora.org (Ashwin Chaugule)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Extending ARM perf-events for multiple PMUs
Date: Mon, 11 Apr 2011 14:00:09 -0400 [thread overview]
Message-ID: <4DA341A9.6060004@codeaurora.org> (raw)
In-Reply-To: <1302349235.9086.1270.camel@twins>
Hi Peter,
On 4/9/2011 7:40 AM, Peter Zijlstra wrote:
>
> So the perf core supports multiple hardware PMUs, but currently only one
> of which can do per-task sampling, if you've got multiple CPU local PMUs
> we need to do a little extra.
Would this restriction be removed if task_struct->perf_event_ctxp[] had
more entries for each PMU_TYPE ?
On a related note, I haven't had time yet to look deeper for a proper fix
for the stale perf_event_ctx pointer issue, other than the one liner in
perf_task_event_sched_in() we discussed about, but that'll need fixing
before more PMU's start popping up.
> What we do for the events is map the provided CPU number to a memory
> controller (cpu_to_node() does that for our case), and then use the
> first online cpu in that node mask to drive the event.
I suppose you're referring to the uncore patches here.
So only one CPU has access to the uncore PMU at a time ?
Cheers,
Ashwin
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-04-11 18:00 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
2011-04-11 17:44 ` Ashwin Chaugule
2011-04-12 17:45 ` Will Deacon
2011-04-11 18:00 ` Ashwin Chaugule [this message]
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=4DA341A9.6060004@codeaurora.org \
--to=ashwinc@codeaurora.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 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.