Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 8/5/08 15:57, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:

>> 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?

I think part of what Ian means is that you may as well have a single
interface into each device model in Xen -- e.g., hpet_reset(), pit_reset(),
and so on. Rather than have separate poweroff/poweron functions. Apart from
the greater simplicity, some models already have a reset interface, and I'm
not sure the implemented poweroff/poweron splits are all correct.

And then, once the poweron calls are all gone, what else does s3_resume
actually have to do?

 -- Keir




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel