All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Wed, 23 Apr 2014 18:08:21 +0100	[thread overview]
Message-ID: <20140423170821.GJ5649@arm.com> (raw)
In-Reply-To: <175CCF5F49938B4D99B2E3EF7F558EBE5507A3B59B@SC-VEXCH4.marvell.com>

On Wed, Apr 23, 2014 at 11:31:09AM +0100, Neil Zhang wrote:
> 
> > -----Original Message-----
> > From: Will Deacon [mailto:will.deacon at arm.com]
> > Sent: 2014?4?22? 18:37
> > To: Neil Zhang
> > Cc: linux at arm.linux.org.uk; linux-arm-kernel at lists.infradead.org;
> > linux-kernel at vger.kernel.org; Sudeep Holla; devicetree at vger.kernel.org
> > Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
> > 
> > Hi Neil,
> > 
> > On Tue, Apr 22, 2014 at 03:26:36AM +0100, Neil Zhang wrote:
> > > 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.
> > >
> > > I made this patch because DS-5 is not working on Marvell's CA7 based SoCs.
> > > And it has consulted Sudeep KarkadaNagesha's patch set for multiple PMUs.
> > >
> > > Thanks Will and Sudeep's suggestion to only save / restore used events.
> > 
> > Whilst this is a step in the right direction, I'd still like to see the save/restore
> > predicated on something in the device-tree or otherwise. Most SoCs *don't*
> > require these registers to be preserved by software, so we need a way to
> > describe that the PMU is in a power-domain where its state is lost when the
> > CPU goes idle.
> > 
> > This doesn't sound like a PMU-specific problem, so there's a possibility that
> > this has been discussed elsewhere, in the context of other IP blocks
> > 
> > [adding the devicetree list in case somebody there is aware of any work in
> > this area]
> > 
> 
> Thanks Will.
> What should I do now?
> Add a filed under PMU or waiting for somebody whether there are general
> supporting for power domain maintain.

I think we need some input from the device-tree guys to see whether they
would object to us solving this locally (in the PMU node) or not.
Personally, I'd much prefer a general way to describe the need for
pm-notifiers, but if that's not being looked at then we can cook something
specifically for our needs.

Will

WARNING: multiple messages have this Message-ID (diff)
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>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Wed, 23 Apr 2014 18:08:21 +0100	[thread overview]
Message-ID: <20140423170821.GJ5649@arm.com> (raw)
In-Reply-To: <175CCF5F49938B4D99B2E3EF7F558EBE5507A3B59B@SC-VEXCH4.marvell.com>

On Wed, Apr 23, 2014 at 11:31:09AM +0100, Neil Zhang wrote:
> 
> > -----Original Message-----
> > From: Will Deacon [mailto:will.deacon@arm.com]
> > Sent: 2014年4月22日 18:37
> > To: Neil Zhang
> > Cc: linux@arm.linux.org.uk; linux-arm-kernel@lists.infradead.org;
> > linux-kernel@vger.kernel.org; Sudeep Holla; devicetree@vger.kernel.org
> > Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
> > 
> > Hi Neil,
> > 
> > On Tue, Apr 22, 2014 at 03:26:36AM +0100, Neil Zhang wrote:
> > > 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.
> > >
> > > I made this patch because DS-5 is not working on Marvell's CA7 based SoCs.
> > > And it has consulted Sudeep KarkadaNagesha's patch set for multiple PMUs.
> > >
> > > Thanks Will and Sudeep's suggestion to only save / restore used events.
> > 
> > Whilst this is a step in the right direction, I'd still like to see the save/restore
> > predicated on something in the device-tree or otherwise. Most SoCs *don't*
> > require these registers to be preserved by software, so we need a way to
> > describe that the PMU is in a power-domain where its state is lost when the
> > CPU goes idle.
> > 
> > This doesn't sound like a PMU-specific problem, so there's a possibility that
> > this has been discussed elsewhere, in the context of other IP blocks
> > 
> > [adding the devicetree list in case somebody there is aware of any work in
> > this area]
> > 
> 
> Thanks Will.
> What should I do now?
> Add a filed under PMU or waiting for somebody whether there are general
> supporting for power domain maintain.

I think we need some input from the device-tree guys to see whether they
would object to us solving this locally (in the PMU node) or not.
Personally, I'd much prefer a general way to describe the need for
pm-notifiers, but if that's not being looked at then we can cook something
specifically for our needs.

Will

  reply	other threads:[~2014-04-23 17:08 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  2:26 [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier Neil Zhang
2014-04-22  2:26 ` Neil Zhang
2014-04-22 10:36 ` Will Deacon
2014-04-22 10:36   ` Will Deacon
2014-04-22 10:36   ` Will Deacon
2014-04-23 10:31   ` Neil Zhang
2014-04-23 10:31     ` Neil Zhang
2014-04-23 10:31     ` Neil Zhang
2014-04-23 17:08     ` Will Deacon [this message]
2014-04-23 17:08       ` Will Deacon
2014-04-30  2:21       ` Neil Zhang
2014-04-30  2:21         ` Neil Zhang
2014-04-30  2:21         ` Neil Zhang
2014-04-30 13:30         ` Sudeep Holla
2014-04-30 13:30           ` Sudeep Holla
2014-04-30 13:30           ` Sudeep Holla
2014-05-05  6:28           ` Neil Zhang
2014-05-05  6:28             ` Neil Zhang
2014-05-05  6:28             ` Neil Zhang
     [not found]           ` <6106CAF835F351419ADA79E4836E6EC71B6A53C826@SC-VEXCH4.marvell.com>
2014-05-12 10:22             ` Neil Zhang
2014-05-12 10:22               ` Neil Zhang
2014-05-12 10:22               ` Neil Zhang
2014-05-13 18:45               ` Will Deacon
2014-05-13 18:45                 ` Will Deacon
2014-05-13 18:45                 ` Will Deacon
2014-05-14  2:28                 ` Neil Zhang
2014-05-14  2:28                   ` Neil Zhang
2014-05-14  2:28                   ` Neil Zhang
2014-05-14  9:31                   ` Sudeep Holla
2014-05-14  9:31                     ` Sudeep Holla
2014-05-14  9:31                     ` Sudeep Holla
2014-05-21 11:46                     ` Neil Zhang
2014-05-21 11:46                       ` Neil Zhang
2014-05-21 11:46                       ` Neil Zhang
2014-06-30 10:39                       ` Neil Zhang
2014-06-30 10:39                         ` Neil Zhang
2014-06-30 10:39                         ` Neil Zhang
2014-07-03 17:57                         ` Will Deacon
2014-07-03 17:57                           ` Will Deacon
2014-07-03 17:57                           ` Will Deacon
2014-10-20  8:46                           ` Neil Zhang
2014-10-20  8:46                             ` Neil Zhang
2014-10-20  8:46                             ` Neil Zhang
2014-10-20  9:16                             ` Sudeep Holla
2014-10-20  9:16                               ` Sudeep Holla
2014-10-20  9:16                               ` Sudeep Holla
2014-10-20  9:20                               ` Will Deacon
2014-10-20  9:20                                 ` Will Deacon
2014-10-20  9:26                                 ` Neil Zhang
2014-10-20  9:26                                   ` Neil Zhang
2014-10-20  9:26                                   ` Neil Zhang
2014-10-20  9:41                                 ` Geert Uytterhoeven
2014-10-20  9:41                                   ` Geert Uytterhoeven
2014-10-20  9:41                                   ` Geert Uytterhoeven
2014-10-21 12:52                                 ` Mathieu Poirier
2014-10-21 12:52                                   ` Mathieu Poirier

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=20140423170821.GJ5649@arm.com \
    --to=will.deacon@arm.com \
    --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.