All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	H Peter Anvin <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tony Luck <tony.luck@intel.com>,
	Arjan van de Ven <arjan.van.de.ven@intel.com>,
	Suresh B Siddha <suresh.b.siddha@intel.com>,
	Len Brown <len.brown@intel.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-pm <linux-pm@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v4 0/7] x86: BSP or CPU0 online/offline
Date: Tue, 06 Dec 2011 19:45:36 +0530	[thread overview]
Message-ID: <4EDE2388.7080806@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111206084230.GC30062@elte.hu>

On 12/06/2011 02:12 PM, Ingo Molnar wrote:

> 
> * Fenghua Yu <fenghua.yu@intel.com> wrote:
> 
>> From: Fenghua Yu <fenghua.yu@intel.com>
>>
>> BSP or CPU0 has been the last obstacle to CPU hotplug on x86. 
>> This patch set implements BSP online and offline and removes 
>> this obstacle to CPU hotplug.

[snip]
> 

> Also, could you please enumerate all limitations that could 
> possibly happen? The documentation has this list right now:
> 
> +1. Resume from hibernate/suspend depends on BSP. Hibernate/suspend will fail if
> +BSP is offline and you need to online BSP before hibernate/suspend can continue.
> 
> This needs to be fixed on some other fashion than warning people 
> in documentation that it would break.
> 


Actually, this patchset does more than just warn people. It has
checks to see if the CPU0 is offline, and if so, it fails the
suspend/hibernate attempt. See patch 7/7
(x86/power/cpu.c: Don't hibernate/suspend if CPU0 is offline)

> Firstly, at minimum a suspend/hibernate attempt should fail in 
> some deterministic fashion.


It does, as mentioned above. In fact, this patchset does it
proactively: whether the hardware/firmware supports suspend/resume
with BSP offlined or not, it just prevents anybody from doing
suspend/hibernate when the boot CPU is offline.

I am not saying that this is the *right* way to do it; I am just
pointing out that this patchset _does_ handle it.

> 
> Secondly, and more importantly, is there *any* hardware in 
> existence that has a BIOS that can suspend/resume successfully 
> with BSP offlined? If such hardware exists then we need to 
> support it properly - initially perhaps by whitelisting such 
> systems.
> 
> Then if demand for this picks up some more intelligent method of 
> cooperating with the firmware could be added: the firmware could 
> actually signal to us whether it supports suspend/resume from 
> other than the boot CPU.
> 

 
Regards,
Srivatsa S. Bhat


  parent reply	other threads:[~2011-12-06 14:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12  5:26 [PATCH v4 0/7] x86: BSP or CPU0 online/offline Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 1/7] x86/topology.c: Support functions for BSP online/offline Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 2/7] x86/common.c: Init BSP data during BSP online Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 3/7] x86/mtrr/main.c: Ask the first online CPU to save mtrr Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 4/7] x86/smpboot.c: Don't offline BSP if any irq can not be migrated out of it Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 5/7] Documentations/cpu-hotplug.tx, kernel-parameters.txt: Add x86 CPU0 online/offline feature Fenghua Yu
2011-11-12  5:26 ` [PATCH v4 6/7] x86/i387.c: Thread xstate is initialized only on BSP once Fenghua Yu
2011-11-13 15:17   ` Brian Gerst
2011-11-12  5:26 ` [PATCH v4 7/7] x86/power/cpu.c: Don't hibernate/suspend if CPU0 is offline Fenghua Yu
2011-12-06  8:42 ` [PATCH v4 0/7] x86: BSP or CPU0 online/offline Ingo Molnar
2011-12-06  8:58   ` Ingo Molnar
2011-12-06  9:52     ` Srivatsa S. Bhat
2011-12-06 10:35       ` Ingo Molnar
2011-12-06 10:47         ` Srivatsa S. Bhat
2011-12-06 11:25           ` Srivatsa S. Bhat
2011-12-06 13:03             ` Borislav Petkov
2011-12-06 13:52               ` Ingo Molnar
2011-12-07  0:04                 ` Yu, Fenghua
2011-12-07  0:15               ` Yu, Fenghua
2011-12-07  7:40                 ` Ingo Molnar
2011-12-07 17:08                   ` Luck, Tony
2011-12-07 22:21                     ` Ingo Molnar
2011-12-08  0:53                       ` Luck, Tony
2011-12-08  4:43                         ` Ingo Molnar
2011-12-06 13:00           ` Borislav Petkov
2011-12-06 14:04             ` Srivatsa S. Bhat
2011-12-06 14:15               ` Borislav Petkov
2011-12-06 14:19                 ` Srivatsa S. Bhat
2011-12-06 14:58     ` Van De Ven, Arjan
2011-12-06 14:15   ` Srivatsa S. Bhat [this message]
2011-12-09  0:41   ` Yu, Fenghua
2011-12-09  7:28     ` Ingo Molnar
2011-12-15 18:38   ` Yu, Fenghua
2011-12-15 18:57     ` Ingo Molnar

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=4EDE2388.7080806@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan.van.de.ven@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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.