diff options
author | Peter Xu <peterx@redhat.com> | 2019-03-29 14:14:21 +0800 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2019-04-02 11:49:14 -0400 |
commit | 2811af3b497b2bfadf38cda0fc92a709f83e8a7e (patch) | |
tree | 685b0c5fc0fa2777f3831c2cb5eb571051f72ff7 /hw/xenpv | |
parent | 20f86a75a75efe7d2743d2f746d2933d01d582f1 (diff) |
intel_iommu: Fix root_scalable migration breakage
When introducing the initial support for scalable mode we added a
new field into vmstate however we blindly migrate that field without
notice. That'll break migration no matter forward or backward.
The normal way should be that we use something like
VMSTATE_UINT32_TEST() or subsections for the new vmstate field however
for this case of vt-d we can even make it simpler because we've
already migrated all the registers and it'll be fairly simple that we
re-generate root_scalable field from the register values during post
load of the device.
Fixes: fb43cf739e ("intel_iommu: scalable mode emulation")
Reviewed-by: Yi Sun <yi.y.sun@linux.intel.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20190329061422.7926-2-peterx@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'hw/xenpv')
0 files changed, 0 insertions, 0 deletions