All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>,
	"Ke, Liping" <liping.ke@intel.com>,
	xen-devel@lists.xensource.com
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"Jiang, Yunhong" <yunhong.jiang@intel.com>,
	"Yu, Ke" <ke.yu@intel.com>
Subject: Re: [PATCH 0/4] HVM Virtual S3
Date: Thu, 08 May 2008 16:20:03 +0100	[thread overview]
Message-ID: <C448D8B3.20787%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <DD74FBB8EE28D441903D56487861CD9D2E0F0FBC@lonpexch01.citrite.net>

On 8/5/08 16:11, "Ian Pratt" <Ian.Pratt@eu.citrix.com> wrote:

> I don't think we need any integration with host S3 as part of the xend
> -- that's a separate issue, maybe an example script that runs (early) as
> part of a host S3 that puts the guests into S3 too.
> 
> I think what we need in xm/xend is a command for informing the guest of
> ACPI events such as lid switch, power cable, power button etc.

We can actually extend the 'xm trigger' command for this with some more
events. 'xm trigger {lid-closed,lid-open}'?

 -- Keir

  reply	other threads:[~2008-05-08 15:20 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  5:13 [PATCH 0/4] HVM Virtual S3 Ke, Liping
2008-05-08  7:02 ` James Harper
2008-05-08  7:10   ` Yu, Ke
2008-05-08  7:24   ` Ke, Liping
2008-05-08 12:25 ` Ian Pratt
2008-05-08 14:57   ` Ke, Liping
2008-05-08 15:03     ` Keir Fraser
2008-05-08 15:10     ` Yu, Ke
2008-05-09  9:58       ` Ke, Liping
2008-05-09 10:10         ` Keir Fraser
2008-05-09 11:59         ` Ian Pratt
2008-05-14  9:50           ` Ke, Liping
2008-05-14 12:17             ` Keir Fraser
2008-05-15  1:31               ` Ke, Liping
2008-05-15  7:33                 ` Keir Fraser
2008-05-15 11:45                   ` Ian Pratt
2008-05-15 11:51                     ` Keir Fraser
2008-05-15 12:42                       ` Ian Pratt
2008-05-15 12:58                         ` Keir Fraser
2008-05-16  1:46                           ` Ke, Liping
2008-05-08 15:11     ` Ian Pratt
2008-05-08 15:20       ` Keir Fraser [this message]
2008-05-08 15:28         ` Yu, Ke
  -- strict thread matches above, loose matches on Subject: below --
2007-05-16 16:48 Yu, Ke
2007-05-16 21:59 ` Keir Fraser
2007-05-16 22:33   ` Keir Fraser
2007-05-17  2:28     ` Yu, Ke
2007-05-18  2:38     ` Tian, Kevin
2007-05-18  6:43       ` Keir Fraser
2007-05-16 22:29 ` Keir Fraser
2007-05-17  2:32   ` Yu, Ke
2007-05-17  7:41     ` Keir Fraser
2007-05-17 12:39       ` Yu, Ke
2007-05-17 12:50         ` Zhang, Jingke
2007-05-17 13:06         ` Keir Fraser
2007-05-17 13:16           ` Yu, Ke
2007-05-17 13:33             ` Keir Fraser
2007-05-18  2:07               ` Tian, Kevin
2007-05-21  3:10           ` Yu, Ke
2007-05-21  6:25             ` Keir Fraser
2007-05-17 20:24   ` Kaushik Barde
2007-05-18  2:05     ` Yu, Ke
2007-05-18  4:22       ` Kaushik Barde
2007-05-18  4:29         ` Yu, Ke
2007-05-17  3:14 ` Kaushik Barde
2007-05-17  4:20   ` Yu, Ke
2007-05-17  9:54     ` Ian Pratt
2007-05-17 14:08       ` Yu, Ke
2007-05-17 14:14         ` Ian Pratt
2007-05-17 14:17           ` Yu, Ke
2007-05-31 10:59             ` Tim Deegan

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=C448D8B3.20787%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=ke.yu@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=liping.ke@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.