| commit | 59046ec29ad4c24391bb9fe1fbdced33557aaa70 | |
| author | Halil Pasic <pasic@linux.vnet.ibm.com> | |
| Fri, 3 Feb 2017 17:52:17 +0000 (3 18:52 +0100) | ||
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Mon, 13 Feb 2017 17:27:13 +0000 (13 17:27 +0000) | ||
| tree | a3f0ec57065500119bc1d2f1a3cd195728dcfcb2 | treesnapshot (tar.gz zip) |
| parent | 0827b9e97d443781a17a21c64695940675aa1f8a | commitdiff |
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>
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>
15 files changed: