From: Will Deacon <will.deacon@arm.com>
To: Neil Zhang <zhangwm@marvell.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sudeep Holla <Sudeep.Holla@arm.com>
Subject: Re: [PATCH v2] ARM: perf: save/restore pmu registers in pm notifier
Date: Tue, 15 Apr 2014 13:41:00 +0100 [thread overview]
Message-ID: <20140415124100.GK17408@arm.com> (raw)
In-Reply-To: <175CCF5F49938B4D99B2E3EF7F558EBE55075F1873@SC-VEXCH4.marvell.com>
On Tue, Apr 15, 2014 at 01:37:17PM +0100, Neil Zhang wrote:
> > On Mon, Apr 14, 2014 at 02:42:22AM +0100, Neil Zhang wrote:
> > > From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
> > >
> > > This adds core support for saving and restoring CPU PMU registers for
> > > suspend/resume support i.e. deeper C-states in cpuidle terms.
> > > This patch adds support only to ARMv7 PMU registers save/restore.
> > > It needs to be extended to xscale and ARMv6 if needed.
> > >
> > > [Neil] We found that DS-5 not work on our CA7 based SoCs.
> > > After debuging, found PMU registers were lost because of core power down.
> > > Then i found Sudeep had a patch to fix it about two years ago but not
> > > in the mainline, just port it.
> >
> > What I don't like about this patch is that we're introducing significant
> > overhead for SoCs that don't require save/restore of the PMU state. I'd much
> > rather see core power down disabled whilst the PMU is in use but, if that's not
> > possible, then I think we need to:
> >
> > (1) Make this conditional for cores that really need it
> >
> > (2) Only save/restore if the PMU is in use (even better, just save/restore
> > the live registers, but that's probably not worth the effort
> > initially).
> >
>
> The patch has check the ARMV7_PMNC_E bit when save / restore,
> so suppose only the core's that use PMU will do the save / restore work.
Seems pretty fragile to base our save/restore decision on the value of one
of the registers, though. What happens if the control register is zeroed by
the core power down?
Will
next prev parent reply other threads:[~2014-04-15 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 1:42 [PATCH v2] ARM: perf: save/restore pmu registers in pm notifier Neil Zhang
2014-04-15 8:47 ` Will Deacon
2014-04-15 12:37 ` Neil Zhang
2014-04-15 12:41 ` Will Deacon [this message]
2014-04-15 12:46 ` Neil Zhang
2014-04-15 12:49 ` Will Deacon
2014-04-15 12:53 ` Neil Zhang
2014-04-15 13:05 ` Sudeep Holla
2014-04-16 2:07 ` Neil Zhang
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=20140415124100.GK17408@arm.com \
--to=will.deacon@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=zhangwm@marvell.com \
/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