From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memory API
Date: Tue, 20 Dec 2011 16:16:31 +0200 [thread overview]
Message-ID: <4EF098BF.7080206@redhat.com> (raw)
In-Reply-To: <4EF09720.9080505@codemonkey.ws>
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
next prev parent reply other threads:[~2011-12-20 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 14:05 [Qemu-devel] [PATCH 0/2] Decouple vmstate from memory API Avi Kivity
2011-12-20 14:05 ` [Qemu-devel] [PATCH 1/2] memory: introduce memory_region_name() Avi Kivity
2011-12-20 14:05 ` [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memory API Avi Kivity
2011-12-20 14:09 ` Anthony Liguori
2011-12-20 14:16 ` Avi Kivity [this message]
2012-01-08 5:14 ` Jordan Justen
2012-01-08 7:23 ` Stefan Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF098BF.7080206@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.