linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] CPU PM notifiers
Date: Tue, 14 Jun 2011 23:00:42 +0200	[thread overview]
Message-ID: <201106142300.42487.rjw@sisk.pl> (raw)
In-Reply-To: <BANLkTi=zTVPkgDO1xXPhypn5Fz6c0PTp79Wq2a6s4jrz3WrJyQ@mail.gmail.com>

On Monday, June 13, 2011, Colin Cross wrote:
> On Mon, Jun 13, 2011 at 11:37 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Monday, June 13, 2011, Colin Cross wrote:
> >> This patch set tries to address Russell's concerns with platform
> >> pm code calling into the driver for every block in the Cortex A9s
> >> during idle, hotplug, and suspend.  The first patch adds cpu pm
> >> notifiers that can be called by platform code, the second uses
> >> the notifier to save and restore the GIC state, and the third
> >> saves the VFP state.
> >>
> >> The notifiers are used for two types of events, CPU PM events and
> >> CPU complex PM events.  CPU PM events are used to save and restore
> >> per-cpu context when a single CPU is preparing to enter or has
> >> just exited a low power state.  For example, the VFP saves the
> >> last thread context, and the GIC saves banked CPU registers.
> >>
> >> CPU complex events are used after all the CPUs in a power domain
> >> have been prepared for the low power state.  The GIC uses these
> >> events to save global register state.
> >>
> >> Platforms that call the cpu_pm APIs must select
> >> CONFIG_ARCH_USES_CPU_PM
> >>
> >> L2 cache is not covered by this patch set, as the determination
> >> of when the L2 is reset and when it is retained is
> >> platform-specific, and most of the APIs necessary are already
> >> present.
> >>
> >>  arch/arm/Kconfig              |    7 ++
> >>  arch/arm/common/gic.c         |  212 +++++++++++++++++++++++++++++++++++++++++
> >>  arch/arm/include/asm/cpu_pm.h |   54 +++++++++++
> >>  arch/arm/kernel/Makefile      |    1 +
> >>  arch/arm/kernel/cpu_pm.c      |  181 +++++++++++++++++++++++++++++++++++
> >
> > Is there any reason why this has to be ARM-specific?  There are other
> > architectures where this kind of feature might make sense (SH and
> > powerpc at least).
> 
> Nothing other than there are currently no adaptations for any drivers
> besides ARM, but I can move it somewhere outside ARM.  Any suggestions
> where?

Well, there is kernel/cpu.c.  It contains mostly CPU hotplug and PM
code at the moment, so it looks like a good place.

> > Besides, is there any overlap between this feature and the CPU hotplug
> > notifiers?
> 
> I don't think so - the hotplug notifiers are used when a CPU is being
> removed from the system, so no saving and restoring is necessary - the
> CPU will be rebooted from scratch.  They are used by systems outside
> the CPU that need to know that a CPU no longer exists.
> 
> CPU PM notifiers are used when a CPU is going through reset in a way
> that should be transparent to most of the system.

Do I guess correctly that you mean cpuidle?

Rafael

  reply	other threads:[~2011-06-14 21:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  0:43 [PATCH 0/3] CPU PM notifiers Colin Cross
2011-06-13  0:43 ` [PATCH 1/3] ARM: Add cpu power management notifiers Colin Cross
2011-06-13  1:57   ` Rob Herring
2011-06-13 22:17   ` Kevin Hilman
2011-06-14  6:15     ` Colin Cross
2011-06-16  0:12       ` Kevin Hilman
2011-06-13  0:43 ` [PATCH 2/3] ARM: gic: Use cpu pm notifiers to save gic state Colin Cross
2011-06-13 10:41   ` Lorenzo Pieralisi
2011-06-13  0:43 ` [PATCH 3/3] ARM: vfp: Use cpu pm notifiers to save vfp state Colin Cross
2011-06-13 18:37 ` [PATCH 0/3] CPU PM notifiers Rafael J. Wysocki
2011-06-13 18:55   ` Colin Cross
2011-06-14 21:00     ` Rafael J. Wysocki [this message]
2011-06-14 21:19       ` Colin Cross
2011-06-14 21:34         ` Rafael J. Wysocki
2011-06-14 21:40           ` Colin Cross
2011-06-14 22:12             ` Rafael J. Wysocki
2011-06-15  6:54               ` Santosh Shilimkar
2011-06-15 23:13               ` Rafael J. Wysocki

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=201106142300.42487.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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;
as well as URLs for NNTP newsgroup(s).