[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 1/5] vl.c: Do not save RAM state when Xen is use
From: |
Anthony PERARD |
Subject: |
Re: [Qemu-devel] [PATCH 1/5] vl.c: Do not save RAM state when Xen is used. |
Date: |
Thu, 24 Nov 2011 18:06:17 +0000 |
On Thu, Nov 24, 2011 at 17:23, Stefano Stabellini
<address@hidden> 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
- [Qemu-devel] [PATCH 0/5] Have a working migration with Xen, Anthony PERARD, 2011/11/24
- [Qemu-devel] [PATCH 1/5] vl.c: Do not save RAM state when Xen is used., Anthony PERARD, 2011/11/24
- [Qemu-devel] [PATCH 3/5] Introduce premigrate RunState., Anthony PERARD, 2011/11/24
- [Qemu-devel] [PATCH 2/5] xen mapcache: Check if a memory space has moved., Anthony PERARD, 2011/11/24
- [Qemu-devel] [PATCH 4/5] xen: Change memory access behavior during migration., Anthony PERARD, 2011/11/24
- [Qemu-devel] [PATCH 5/5] vga-cirrus: Workaround during restore when using Xen., Anthony PERARD, 2011/11/24