All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <jbeulich@novell.com>, Kevin Tian <kevin.tian@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: poweroff in 3.2 and 3.3
Date: Thu, 20 Nov 2008 08:18:57 +0000	[thread overview]
Message-ID: <C54ACDF1.1F6D8%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49252B4B.76E4.0078.0@novell.com>

On 20/11/08 08:18, "Jan Beulich" <jbeulich@novell.com> wrote:

>> Comment says "Only s3 is using this path", instead of "this path
>> can only be used by s3". :-) At that time cpu online/offline is not
>> supported and thus only s3 is the user on that path. If you look at
>> latest xen upstream with cpu offline support, that comment went
>> away.
> 
> But my point is that this is wrong (no matter how it's worded): entering
> S5 also uses this path, and in that case there's nothing that stops
> non-current vCPU-s of dom0.

If you're powering off, why does it matter if VCPUs are paused or not?

 -- Keir

  reply	other threads:[~2008-11-20  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 13:18 poweroff in 3.2 and 3.3 Jan Beulich
2008-11-19 13:21 ` Keir Fraser
2008-11-20  2:39   ` Tian, Kevin
2008-11-20  8:00     ` Keir Fraser
2008-11-20  8:11       ` Tian, Kevin
2008-11-20  8:16         ` Keir Fraser
2008-11-20  8:21           ` Tian, Kevin
2008-11-20  8:51             ` Keir Fraser
2008-11-20  8:56               ` Tian, Kevin
2008-11-20  8:18     ` Jan Beulich
2008-11-20  8:18       ` Keir Fraser [this message]
2008-11-20  8:30         ` Jan Beulich
2008-11-20  8:36           ` Tian, Kevin
2008-11-20  8:19       ` Tian, Kevin
2008-11-20  8:31         ` Jan Beulich
2008-11-20  8:23       ` Tian, Kevin

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=C54ACDF1.1F6D8%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=jbeulich@novell.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.