From: ashwinc@codeaurora.org (Ashwin Chaugule)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: perf: add PMU hotplug notifier
Date: Thu, 23 Feb 2012 11:12:59 -0500 [thread overview]
Message-ID: <4F46658B.3030903@codeaurora.org> (raw)
In-Reply-To: <20120223160450.GL29450@mudshark.cambridge.arm.com>
On 2/23/2012 11:04 AM, Will Deacon wrote:
>
> Ok. Note that the perf core will actually destroy perf events on a hotplug
> down notification, so profiling runs will be dead on that core even if it
> comes back up.
>
> This patch just ensures that we have a sane state in the control registers
> given that their state is UNKNOWN out of reset. Adding full hotplug support
> to perf (that is, supporting hotplug events during a run and representing
> that in a meaningful way) is a larger issue.
>
>>> I'll send a link to my code once the git server is up. It's a bit flaky today.
>
> Ok, cool. Are you happy with me to proceed with the current code for the
> time being?
>
Sure. We'll need to be able to distinguish between a hotplug and a CPU
power-collapse / deep sleep / what-have-you state in this code at some
point since they all have a different effect on the PMU regs.
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:[~2012-02-23 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKHPGBaY1OFiVubic+f1vxxzNeKjmzibxraBg8eNxZnJbhYi+A@mail.gmail.com>
2012-02-23 15:57 ` [PATCH] ARM: perf: add PMU hotplug notifier Ashwin Chaugule
2012-02-23 16:00 ` Ashwin Chaugule
2012-02-23 16:04 ` Will Deacon
2012-02-23 16:12 ` Ashwin Chaugule [this message]
2012-02-23 16:31 ` [PATCH] ARM: perf: add PMU hotplug notifiery Lorenzo Pieralisi
2012-02-23 15:41 [PATCH] ARM: perf: add PMU hotplug notifier Will Deacon
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=4F46658B.3030903@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.