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

["Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>]

> > 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.
> 
> S3 suspend is enacted by an I/O port write from the guest, trapped by
> qemu,
> so the final reset of machine state is synchronously triggered by the
> tools
> anyway.

OK, as long as qemu-dm communicates this via xenstore.
 
> As for pause-vs-block I think this is just a matter of terminology. At
> the end of the day we want the domain to not run until s3-resume is
> triggered.
> The natural way to do this within the hypervisor is to maintain a per-
> domain is_s3_suspended flag and domain_[un]pause() when this flag
toggles.

We wouldn't need to do the pause if the code after the magic port write
did "cli;hlt". Does it do this or loop?
[On real hardware the effect of the port write wouldn't be immediate, so
it must do something]

Ian


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