| /qemu/hw/xtensa/ |
| H A D | sim.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | xtfpga.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/include/hw/ |
| H A D | hw.h | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/mips/ |
| H A D | mipssim.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | fuloong2e.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | jazz.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/display/ |
| H A D | g364fb.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | tcx.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | vmware_vga.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/m68k/ |
| H A D | an5206.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | mcf5208.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/ppc/ |
| H A D | ppc4xx_devs.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | virtex_ml507.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/arm/ |
| H A D | omap_sx1.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | strongarm.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | integratorcp.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | omap1.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | realview.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/alpha/ |
| H A D | typhoon.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/microblaze/ |
| H A D | petalogix_s3adsp1800_mmu.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | petalogix_ml605_mmu.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/sparc/ |
| H A D | leon3.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/misc/ |
| H A D | ivshmem-pci.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/sh4/ |
| H A D | r2d.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /qemu/hw/block/ |
| H A D | pflash_cfi02.c | c5705a7728b4a6bc9e4f2d35911adbaf28042b25 Tue Dec 20 13:59:12 UTC 2011 Avi Kivity <avi@redhat.com> vmstate, memory: decouple vmstate from memory API
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.
Signed-off-by: Avi Kivity <avi@redhat.com>
|