xen-devel
RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3
To: |
"Yu, Ke" <ke.yu@xxxxxxxxx>, "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3 |
From: |
"Ke, Liping" <liping.ke@xxxxxxxxx> |
Date: |
Fri, 9 May 2008 17:58:04 +0800 |
Cc: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> |
Delivery-date: |
Fri, 09 May 2008 02:58:34 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<1104166E0B63A341805FDB977862AAD20174A0D1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
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: |
<391BF3CDD2DC0848B40ACB72FA97AD590352E058@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <DD74FBB8EE28D441903D56487861CD9D2DFDA9B3@xxxxxxxxxxxxxxxxxxxxxx> <391BF3CDD2DC0848B40ACB72FA97AD590352E41A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1104166E0B63A341805FDB977862AAD20174A0D1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Aciwyj3GC5kFZyVcS9eJk6QW6cxy6gAO58GAAASSNxAAAQ9pEAAnjI9g |
Thread-topic: |
[Xen-devel] [PATCH 0/4] HVM Virtual S3 |
>>>
>>> Further, do we actually need the s3 resume hypercall? Couldn't we
>>> just put the VCPUs and xen-emulated devices into the right state for
>>> resume at the end of s3 sleep and just leave the domain paused (i.e.
>>> unscheduled)?
>> As I can understand, when S3, HVM will perform like native-machine
>> S3, all execution context are in memory When resume back, jump to the
>> CS/EIP, those vcpus resume execution normally.
>> Ke& Kevin, any coments here?
>
> That is good idea. Basically we will combine suspend/resume into one
> logic. And use "xm unpause" for resume. We will look into more.
>
Hi, Ke and Ian
Today I am trying this idea, I found combining S3
sus/resume+domain_pause, and then
use domain_unpause letting domain back works fine.
Yet when I am trying xm save after pausing domain, I found if a domain
not running,
Xm save will reject the save request.
So I want to know whether domain running is a must for xm save
operation?
Thanks& Regards,
Criping
>>>
>>> Many Thanks,
>>> Ian
>
> Thanks for the valuable comments :)
>
> Best Regards
> Ke
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH 0/4] HVM Virtual S3, Ke, Liping
- RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3, James Harper
- 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, 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
|
|
|