All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Yang <leoli@freescale.com>
To: chen gong <gong.chen@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: nonboot cpu on SMP suspend
Date: Thu, 19 Mar 2009 15:18:27 +0800	[thread overview]
Message-ID: <2a27d3730903190018h1a0f5b6asf5cf2002fe3504fb@mail.gmail.com> (raw)
In-Reply-To: <49C1EE7D.5070507@linux.intel.com>

On Thu, Mar 19, 2009 at 3:04 PM, chen gong <gong.chen@linux.intel.com> wrote:
> Rafael J. Wysocki 写道:
>>
>> On Wednesday 18 March 2009, Li Yang wrote:
>>>
>>> Hi all,
>>>
>>> I'm curious why we need to un-plug all the nonboot cpus before suspend
>>> and start them all over again after the suspend(ACPI sleep)?  I mean
>>> if we can bring the booting cpu back to the exact state as before
>>> suspend, why can't we just do the same for non-booting cpus?  And that
>>> will be much faster.  Any thought?  Thanks.
>>
>> Because we need to enter the BIOS with one CPU on-line only.
>>
> You mean only one CPU can be supported by BIOS when suspend/resume ?

If so, is it a defect of x86 BIOS?  And is it true that for other
architectures without a BIOS there won't be such a limitation if the
boot code is sane?  Thanks

- Leo

  reply	other threads:[~2009-03-19  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  6:25 nonboot cpu on SMP suspend Li Yang
2009-03-18 23:00 ` Rafael J. Wysocki
2009-03-19  7:04   ` chen gong
2009-03-19  7:18     ` Li Yang [this message]
2009-03-19 12:30       ` Rafael J. Wysocki
2009-03-20 18:58 ` Pavel Machek
2009-03-23  7:15   ` Li Yang
2009-03-23 10:38     ` Pavel Machek

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=2a27d3730903190018h1a0f5b6asf5cf2002fe3504fb@mail.gmail.com \
    --to=leoli@freescale.com \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.