From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/8] Convert live migration to memory API
Date: Wed, 21 Dec 2011 07:59:06 -0600 [thread overview]
Message-ID: <4EF1E62A.5090508@codemonkey.ws> (raw)
In-Reply-To: <1324474477-22267-1-git-send-email-avi@redhat.com>
On 12/21/2011 07:34 AM, Avi Kivity wrote:
> These patches, on top of "vmstate, memory: decouple vmstate from memory API",
> convert live migration to use the memory API.
>
> Patch 4 is an ABI change, please review carefully.
Using ram_addr_t for migration was badly, badly broken. I think it's been long
enough that we can safely remove that logic.
Other than my request for a better commit message, this whole series:
Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
Regards,
Anthony Liguori
>
> Avi Kivity (8):
> Store MemoryRegion in RAMBlock
> Switch ram_save to the memory API
> Sort RAMBlocks by ID for migration, not by ram_addr
> Remove support for version 3 ram_load
> Convert ram_load() to the memory API
> memory: obsolete cpu_physical_memory_[gs]et_dirty_tracking()
> xen: convert framebuffer dirty tracking to memory API
> memory: obsolete more dirty memory related functions
>
> arch_init.c | 71 +++++++++++++++++++-----------------------------------
> cpu-all.h | 54 +-----------------------------------------
> exec-obsolete.h | 51 +++++++++++++++++++++++++++++++++++++++
> exec.c | 11 +-------
> memory.c | 2 +
> xen-all.c | 5 +--
> 6 files changed, 82 insertions(+), 112 deletions(-)
>
prev parent reply other threads:[~2011-12-21 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 13:34 [Qemu-devel] [PATCH 0/8] Convert live migration to memory API Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 1/8] Store MemoryRegion in RAMBlock Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 2/8] Switch ram_save to the memory API Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 3/8] Sort RAMBlocks by ID for migration, not by ram_addr Avi Kivity
2011-12-21 13:55 ` Anthony Liguori
2011-12-21 15:15 ` Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 4/8] Remove support for version 3 ram_load Avi Kivity
2011-12-21 13:57 ` Anthony Liguori
2011-12-21 15:18 ` Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 5/8] Convert ram_load() to the memory API Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 6/8] memory: obsolete cpu_physical_memory_[gs]et_dirty_tracking() Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 7/8] xen: convert framebuffer dirty tracking to memory API Avi Kivity
2011-12-21 13:34 ` [Qemu-devel] [PATCH 8/8] memory: obsolete more dirty memory related functions Avi Kivity
2011-12-21 13:59 ` Anthony Liguori [this message]
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=4EF1E62A.5090508@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).