From: Avi Kivity <avi@redhat.com>
To: quintela@redhat.com, Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] Decouple vmstate from memory API
Date: Tue, 20 Dec 2011 16:05:12 +0200 [thread overview]
Message-ID: <1324389914-12246-1-git-send-email-avi@redhat.com> (raw)
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.
Avi Kivity (2):
memory: introduce memory_region_name()
vmstate, memory: decouple vmstate from memory API
Makefile.objs | 2 +-
Makefile.target | 2 +-
cpu-common.h | 1 +
exec-obsolete.h | 6 ++----
exec.c | 31 ++++++++++++++++++++++---------
hw/alpha_typhoon.c | 3 ++-
hw/an5206.c | 6 ++++--
hw/armv7m.c | 9 ++++++---
hw/axis_dev88.c | 6 ++++--
hw/dummy_m68k.c | 3 ++-
hw/g364fb.c | 3 ++-
hw/hw.h | 5 +++++
hw/integratorcp.c | 6 ++++--
hw/ivshmem.c | 7 +++++--
hw/leon3.c | 6 ++++--
hw/lm32_boards.c | 6 ++++--
hw/mainstone.c | 3 ++-
hw/mcf5208.c | 6 ++++--
hw/milkymist-minimac2.c | 3 ++-
hw/milkymist-softusb.c | 6 ++++--
hw/milkymist.c | 3 ++-
hw/mips_fulong2e.c | 6 ++++--
hw/mips_jazz.c | 9 ++++++---
hw/mips_malta.c | 9 ++++++---
hw/mips_mipssim.c | 6 ++++--
hw/mips_r4k.c | 6 ++++--
hw/musicpal.c | 6 ++++--
hw/omap1.c | 6 ++++--
hw/omap2.c | 6 ++++--
hw/omap_sx1.c | 6 ++++--
hw/onenand.c | 3 ++-
hw/palm.c | 3 ++-
hw/pc.c | 9 ++++++---
hw/pci.c | 4 +++-
hw/petalogix_ml605_mmu.c | 6 ++++--
hw/petalogix_s3adsp1800_mmu.c | 7 ++++---
hw/pflash_cfi01.c | 4 +++-
hw/pflash_cfi02.c | 3 ++-
hw/ppc405_boards.c | 18 ++++++++++++------
hw/ppc405_uc.c | 3 ++-
hw/ppc4xx_devs.c | 3 ++-
hw/ppc_newworld.c | 6 ++++--
hw/ppc_oldworld.c | 6 ++++--
hw/ppc_prep.c | 6 ++++--
hw/ppce500_mpc8544ds.c | 3 ++-
hw/pxa2xx.c | 12 ++++++++----
hw/r2d.c | 3 ++-
hw/realview.c | 9 ++++++---
hw/s390-virtio.c | 3 ++-
hw/shix.c | 9 ++++++---
hw/sm501.c | 3 ++-
hw/spitz.c | 3 ++-
hw/strongarm.c | 3 ++-
hw/sun4m.c | 12 ++++++++----
hw/sun4u.c | 6 ++++--
hw/tc6393xb.c | 3 ++-
hw/tcx.c | 3 ++-
hw/tosa.c | 3 ++-
hw/versatilepb.c | 3 ++-
hw/vexpress.c | 12 ++++++++----
hw/vga.c | 3 ++-
hw/virtex_ml507.c | 3 ++-
hw/vmware_vga.c | 3 ++-
hw/xtensa_lx60.c | 9 ++++++---
hw/xtensa_sim.c | 6 ++++--
memory.c | 14 ++++++++------
memory.h | 27 ++++++++++++---------------
savevm.c | 17 +++++++++++++++++
xen-all.c | 3 ++-
69 files changed, 292 insertions(+), 147 deletions(-)
--
1.7.7.1
next reply other threads:[~2011-12-20 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 14:05 Avi Kivity [this message]
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
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=1324389914-12246-1-git-send-email-avi@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 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).