|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3
To: |
"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3 |
From: |
"Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx> |
Date: |
Thu, 15 May 2008 12:45:22 +0100 |
Cc: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx> |
Delivery-date: |
Thu, 15 May 2008 04:46:25 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<C451A5F7.187C2%keir.fraser@xxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<391BF3CDD2DC0848B40ACB72FA97AD59035AADD9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C451A5F7.187C2%keir.fraser@xxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Aciwyj3GC5kFZyVcS9eJk6QW6cxy6gAO58GAAASSNxAAAQ9pEAAnjI9gAAQtZQAA9rPlAAAFlo6tABrTxrAADZF8SQAIt2zQ |
Thread-topic: |
[Xen-devel] [PATCH 0/4] HVM Virtual S3 |
> The 'pause' state visible to tools is a specific type of
> domain_pause(), and
> *has* to be entered via the pause domctl hypercall. So don't worry --
> your new type of pause should stack on top of 'xm pause/unpause' no
problem.
In fact, does the S3 suspended guest need to go into a pause state at
all? Presumably we could just let it block?
Xend does need to be able to know when the S3 suspend has actually
happened -- there should probably be a VIRQ for this.
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, (continued)
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Yu, Ke
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ian Pratt
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3,
Ian Pratt <=
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ian Pratt
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ian Pratt
- Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Keir Fraser
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, Yu, Ke
|
|
|
|
|