From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: pvops dom0 work roadmap
Date: Thu, 20 Aug 2009 09:43:18 -0700 [thread overview]
Message-ID: <4A8D7D26.8060708@goop.org> (raw)
In-Reply-To: <4A8D3D290200007800010C65@vpn.id2.novell.com>
On 08/20/09 03:10, Jan Beulich wrote:
> Yes, but Dom0 has to tell Xen when this is to happen (see
> acpi_enter_sleep_state() in the 2.6.18 tree).
Oh, that's a bit awkward. I'd assumed that dom0 would do a shutdown
hypercall and Xen would sort out the actual shutdown part.
> I think you had discussed
> this with the ACPI folks already, and your initial approach was disliked
> for whatever reason...
Yes, we haven't converged on something upstreamable yet, but
rebase/master has everything needed for S3, and I think that's enough
for shutdown? I haven't tried shutdown lately, but reboot works for me;
is that the same path?
J
next prev parent reply other threads:[~2009-08-20 16:43 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 18:43 pvops dom0 work roadmap Jeremy Fitzhardinge
2009-08-18 20:07 ` Pasi Kärkkäinen
2009-08-18 20:12 ` Jeremy Fitzhardinge
2009-08-18 22:41 ` Pasi Kärkkäinen
2009-08-19 4:16 ` Boris Derzhavets
2009-08-19 7:09 ` pvops dom0 work roadmap / Fedora 11 libvirt problems with Xen 3.4 Pasi Kärkkäinen
2009-08-19 7:27 ` Boris Derzhavets
2009-08-19 9:54 ` Boris Derzhavets
2009-08-19 10:14 ` Boris Derzhavets
2009-08-19 10:27 ` Pasi Kärkkäinen
2009-08-19 12:21 ` Boris Derzhavets
2009-08-19 12:37 ` Pasi Kärkkäinen
2009-08-19 13:05 ` Boris Derzhavets
2009-08-19 13:26 ` Boris Derzhavets
2009-08-19 13:35 ` Boris Derzhavets
2009-08-19 14:32 ` Pasi Kärkkäinen
2009-08-19 15:40 ` Boris Derzhavets
2009-08-19 15:49 ` Boris Derzhavets
2009-08-19 17:00 ` pvops dom0 work roadmap / Fedora 11 domU/guest pygrub grub.conf timeout=0 problem Pasi Kärkkäinen
2009-08-19 17:23 ` Pasi Kärkkäinen
2009-08-19 13:26 ` pvops dom0 work roadmap Konrad Rzeszutek Wilk
2009-08-19 16:19 ` Jeremy Fitzhardinge
2009-08-19 16:54 ` Pasi Kärkkäinen
2009-08-19 17:04 ` Jeremy Fitzhardinge
2009-08-20 10:10 ` Jan Beulich
2009-08-20 16:43 ` Jeremy Fitzhardinge [this message]
2009-08-21 6:58 ` Jan Beulich
2009-08-19 17:17 ` Jeremy Fitzhardinge
2009-08-19 17:45 ` Konrad Rzeszutek Wilk
2009-08-19 19:06 ` Jeremy Fitzhardinge
2009-08-19 19:14 ` Konrad Rzeszutek Wilk
2009-08-20 15:49 ` Gianluca Guida
2009-08-20 16:39 ` Konrad Rzeszutek Wilk
2009-08-20 16:36 ` Gianluca Guida
2009-08-20 17:11 ` Konrad Rzeszutek Wilk
2009-08-19 15:27 ` M A Young
2009-08-19 16:21 ` Jeremy Fitzhardinge
2009-08-19 17:35 ` M A Young
2009-08-19 19:08 ` Jeremy Fitzhardinge
2009-08-20 10:43 ` M A Young
2009-08-20 16:22 ` Jeremy Fitzhardinge
2009-08-20 23:17 ` M A Young
2009-08-20 23:39 ` Jeremy Fitzhardinge
2009-08-20 0:25 ` Daniel Schroeder
2009-08-20 0:42 ` Jeremy Fitzhardinge
2009-08-20 0:46 ` Jeremy Fitzhardinge
2009-08-20 1:56 ` Yu, Ke
2009-09-02 6:47 ` Boris Derzhavets
2009-09-02 13:43 ` Konrad Rzeszutek Wilk
2009-09-02 14:02 ` Boris Derzhavets
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 13:50 Boris Derzhavets
2009-09-02 17:23 Boris Derzhavets
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=4A8D7D26.8060708@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=konrad.wilk@oracle.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.