| commit | 1dd713837cac8ec5a97d3b8492d72ce5ac94803c | |
| author | Michael S. Tsirkin <mst@redhat.com> | |
| Fri, 11 Oct 2019 13:58:03 +0000 (11 15:58 +0200) | ||
| committer | Jason Wang <jasowang@redhat.com> | |
| Tue, 29 Oct 2019 02:28:07 +0000 (29 10:28 +0800) | ||
| tree | 807a8d973bbb2e93f2caa1b5951381c9318007a3 | treesnapshot (tar.gz zip) |
| parent | 34ea023d4b959f35be8771470483c57dbbe2447d | commitdiff |
virtio: new post_load hook
Post load hook in virtio vmsd is called early while device is processed,
and when VirtIODevice core isn't fully initialized. Most device
specific code isn't ready to deal with a device in such state, and
behaves weirdly.
Add a new post_load hook in a device class instead. Devices should use
this unless they specifically want to verify the migration stream as
it's processed, e.g. for bounds checking.
Cc: qemu-stable@nongnu.org
Suggested-by: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Mikhail Sennikovsky <mikhail.sennikovskii@cloud.ionos.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Post load hook in virtio vmsd is called early while device is processed,
and when VirtIODevice core isn't fully initialized. Most device
specific code isn't ready to deal with a device in such state, and
behaves weirdly.
Add a new post_load hook in a device class instead. Devices should use
this unless they specifically want to verify the migration stream as
it's processed, e.g. for bounds checking.
Cc: qemu-stable@nongnu.org
Suggested-by: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Mikhail Sennikovsky <mikhail.sennikovskii@cloud.ionos.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
| hw/virtio/virtio.c | diffblobblamehistory | |
| include/hw/virtio/virtio.h | diffblobblamehistory |