|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [Patch 4/4]: Xend interface for HVM S3
Ke, Liping writes ("RE: [Xen-devel] [Patch 4/4]: Xend interface for HVM S3"):
> Since hvm suspend is initiated by HVM guest, so only xm resume entry
> is reused here.
I see. That seems ... odd.
> > What if the guest is in the middle of going into one kind of suspend
> > when a request arrives to put it into a different kind of suspend ?
> > (Users often make multiple similar requests if they think the first
> > request isn't working.)
>
> Currently it will do HVM_S3_Resume when we detect it is hvm domain
> in domain_resume temporarially. I think it is a temporary solution.
> I think there are only two combinations: if it is save, resume -> restore.
> Otherwise, resume->s3 wake up for HVM.
Can the guest be saved (with `xm suspend') while it is suspending
(into HVM S3) ? If so then you may have to resume it twice ...
> So do you think which way is better, reuse xm resume or not?
Sad though I am to say it, I think we need yet another kind of
resumption/restoration/restarting/etc.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|