From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Cc: "Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: poweroff in 3.2 and 3.3
Date: Wed, 19 Nov 2008 13:21:50 +0000 [thread overview]
Message-ID: <C549C36E.29329%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49242037.76E4.0078.0@novell.com>
On 19/11/08 13:18, "Jan Beulich" <jbeulich@novell.com> wrote:
> The hypervisor appears to make the assumption that all but the vCPU
> XENPF_enter_acpi_sleep is being called on are down (in 3.2 because the
> sender of the event check IPI assumes the remote CPU is idle, in 3.3 by
> and explicit check in __cpu_disable() - here we also have an incorrect
> comment stating that this path can only be used when entering S3).
>
> I can't, however, see how this would be guaranteed on the kernel side
> (and apart from that I don't think the hypervisor should be dependent on
> kernel behavior here, even if it's dom0). Shouldn't therefore
> freeze_domains() not only freeze all DomU-s, but also all non-current
> vCPU-s of Dom0?
Kevin Tian is probably best placed to answer this. I'm happy to see this
added if he agrees.
-- Keir
next prev parent reply other threads:[~2008-11-19 13:21 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 [this message]
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
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=C549C36E.29329%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.