[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memo
|
From: |
Avi Kivity |
|
Subject: |
Re: [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memory API |
|
Date: |
Tue, 20 Dec 2011 16:16:31 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0 |
On 12/20/2011 04:09 PM, Anthony Liguori wrote:
> On 12/20/2011 08:05 AM, Avi Kivity wrote:
>> Currently creating a memory region automatically registers it for
>> live migration. This differs from other state (which is enumerated
>> in a VMStateDescription structure) and ties the live migration code
>> into the memory core.
>>
>> Decouple the two by introducing a separate API, vmstate_register_ram(),
>> for registering a RAM block for migration. Currently the same
>> implementation is reused, but later it can be moved into a separate
>> list,
>> and registrations can be moved to VMStateDescription blocks.
>
> Makes a lot of sense to me. Did you write a script to do the conversion?
No, manual conversion. Had to add vmstate_unregister_ram() in the few
places that had destructors.
--
error compiling committee.c: too many arguments to function