On Thu, Nov 24, 2011 at 17:23, Stefano Stabellini <stefano.stabell...@eu.citrix.com> wrote: > On Thu, 24 Nov 2011, Anthony PERARD wrote: >> In Xen case, the guest RAM is not handle by QEMU, and it is saved by Xen >> tools. >> So, we just avoid to register the RAM save state handler. > > Maybe we can unregister these handlers in the Xen specific > initialization code, before we start receiving save/restore requests, > otherwise we could have a nasty race condition.
One argument for my patch was: Not register at all the "ram" save/restore function when Xen is enable make the code more clear: no ram saved with Xen. On the other hand, unregister the "ram" save/restore function in the Xen code, will remove this if(xen) from the generic code. I'm fine with both. Regards, -- Anthony PERARD
