|
Re: [PATCH 0/5] KVM paravirt_ops implementation: msg#00612emulators.kvm.devel
Anthony Liguori wrote: > The real trick is doing it without the guest being involved at all. > Right now, it won't be a problem in KVM since the hypercall page only > differs by a single instruction across platforms. In the future, > we'll have to be smarter and wait for all VCPUs to leave the hypercall > page. Well, you could just fake the whole acpi suspend/resume ;) >> The tricky part for Xen in all this is how to make sure all mfn >> references are visible to the hypervisor/toolstack so they can be >> remapped; hypercall page contents are not a concern by comparison. > > I don't know HVM save/resume all that well but I think it's a similar > model where the guest isn't involved. Yes, the guest has little to nothing to do. > They may have a similar issue when using PV drivers. Hm, not sure. J ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [PATCH 0/5] KVM paravirt_ops implementation: 00612, Anthony Liguori |
|---|---|
| Next by Date: | Re: [PATCH 0/5] KVM paravirt_ops implementation: 00612, Anthony Liguori |
| Previous by Thread: | Re: [PATCH 0/5] KVM paravirt_ops implementationi: 00612, Anthony Liguori |
| Next by Thread: | Re: [PATCH 0/5] KVM paravirt_ops implementation: 00612, Zachary Amsden |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |