linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm: dis-allow hotplug on MSM
Date: Thu, 30 Sep 2010 13:40:45 -0700	[thread overview]
Message-ID: <1285879245.14953.29.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100930201749.GA11660@n2100.arm.linux.org.uk>

On Thu, 2010-09-30 at 21:17 +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 30, 2010 at 01:08:07PM -0700, Daniel Walker wrote:
> > That's actually what I had original, Russell offered this as an
> > alternative. Now that I think about the stubs tho, I'm not sure it's
> > that bad an idea. All the stubs would do is not put the core into a
> > lower powermode, but would allow suspend. It wouldn't be very
> > efficient , but suspend would work.
> 
> If you just provide empty stubs, esp. for platform_cpu_die(), then an
> attempt to take a CPU offline will result in it immediately restarting
> back into the kernel - which will probably result in an oops as the
> kernel won't be expecting the CPU to come back.

Ok ..

> If you make them spin, you'll eat power until the system powers them off.
> As things currently stand though, we don't have enough code out of the
> init sections to allow a SMP restart from power-off.  So, S2RAM isn't
> going to work on secondary processors at the moment _anyway_.

When you say "SMP restart" do you mean resume? If I did make them spin
wouldn't suspend and resume work at that point?

> Current CPU hotplug implementations are based around taking CPUs offline
> without powering them off for run-time power saving only.

What I was thinking with the stubs is to fake the offlining. So it's not
power efficient , but suspend still works.

Daniel

-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-09-30 20:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 19:58 [GIT PULL] generic arm MSM changes for v2.6.37 Daniel Walker
2010-09-09 19:58 ` [PATCH 1/4] arm: Kconfig option for ARCH_MSM_SCORPIONMP Daniel Walker
2010-09-10 10:14   ` Sergei Shtylyov
2010-09-10 14:51     ` Uwe Kleine-König
2010-09-10 15:04       ` Daniel Walker
2010-09-11 11:02       ` Sergei Shtylyov
2010-09-10 15:15     ` Lorenzo Pieralisi
2010-09-10 20:36   ` Russell King - ARM Linux
2010-09-10 21:01     ` Daniel Walker
2010-09-09 19:58 ` [PATCH 2/4] arm: dis-allow hotplug on MSM Daniel Walker
2010-09-30  7:19   ` Pavel Machek
2010-09-30 16:45     ` Daniel Walker
2010-09-30 18:09       ` Daniel Walker
2010-09-30 19:52         ` Pavel Machek
2010-09-30 19:55           ` Daniel Walker
2010-09-30 20:02             ` Pavel Machek
2010-09-30 20:08               ` Daniel Walker
2010-09-30 20:17                 ` Russell King - ARM Linux
2010-09-30 20:40                   ` Daniel Walker [this message]
2010-09-30 20:48                     ` Russell King - ARM Linux
2010-09-09 19:58 ` [PATCH 3/4] arm: mm: add proc info for ARM11MPCore/Cortex-A9 from ARM Daniel Walker
2010-09-13 12:05   ` Catalin Marinas
2010-09-09 19:58 ` [PATCH 4/4] GIC: Dont disable INT in ack callback Daniel Walker

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=1285879245.14953.29.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@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 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).