qemu-e2k/target
Halil Pasic 59046ec29a migration: consolidate VMStateField.start
The member VMStateField.start is used for two things, partial data
migration for VBUFFER data (basically provide migration for a
sub-buffer) and for locating next in QTAILQ.

The implementation of the VBUFFER feature is broken when VMSTATE_ALLOC
is used. This however goes unnoticed because actually partial migration
for VBUFFER is not used at all.

Let's consolidate the usage of VMStateField.start by removing support
for partial migration for VBUFFER.

Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>

Message-Id: <20170203175217.45562-1-pasic@linux.vnet.ibm.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
2017-02-13 17:27:13 +00:00
..
alpha migration: extend VMStateInfo 2017-01-24 17:54:47 +00:00
arm target-arm: Enable vPMU support under TCG mode 2017-02-10 17:40:28 +00:00
cris
hppa target/hppa: Fix gdb_write_register 2017-02-06 18:25:31 -08:00
i386 pc: Enable vmware-cpuid-freq CPU option for 2.9+ machine types 2017-01-27 18:07:58 +01:00
lm32
m68k This is the same as the v3 posted except a re-base and a few extra signoffs 2017-01-16 18:23:02 +00:00
microblaze
mips migration: extend VMStateInfo 2017-01-24 17:54:47 +00:00
moxie
nios2 nios2: Add architecture emulation support 2017-01-24 13:10:35 -08:00
openrisc
ppc ppc/kvm: Handle the "family" CPU via alias instead of registering new types 2017-02-02 09:30:07 +11:00
s390x migration: consolidate VMStateField.start 2017-02-13 17:27:13 +00:00
sh4
sparc migration: extend VMStateInfo 2017-01-24 17:54:47 +00:00
tilegx
tricore
unicore32
xtensa target/xtensa updates: 2017-01-25 16:36:57 +00:00