From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Jan Beulich <jbeulich@novell.com>,
"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:00:50 +0000 [thread overview]
Message-ID: <C54AC9B2.1F6CE%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD601E23B3F@pdsmsx502.ccr.corp.intel.com>
On 20/11/08 02:39, "Tian, Kevin" <kevin.tian@intel.com> wrote:
> However I'm considering the point whether Xen can simply reject the
> s3 request, when observing non-current vcpus still alive. Domain can
> be in trouble if unaware of underlying sleep phase, such time keeping
> and softlockup warning. More seriously, domain with passthrough
> devices can't recover device state since it's even not notified to save
> context. Opinions?
What would you warn on?
- VCPUs still exist?
- VCPUs still online?
- VCPUs not paused?
- VCPUs not 'paused_by_system_controller'?
I'm not sure what the WARN_ON() condition would be. A forceful
domain_pause()/vcpu_pause() is a good idea anyway.
-- Keir
next prev parent reply other threads:[~2008-11-20 8:00 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 [this message]
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=C54AC9B2.1F6CE%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.