KVM: x86: do not save guest-unsupported XSAVE state
authorRadim Krčmář <rkrcmar@redhat.com>
Wed, 1 Feb 2017 13:19:53 +0000 (14:19 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 9 Feb 2017 07:08:29 +0000 (08:08 +0100)
commit0dcbd0aa44e6b2aa725175dd5933cb706fb1e2c5
tree4b729a809375cbb769a73aa21e4851672c1d3710
parentbc05a2e940fe96fbacf879e73139d8a66c39ab8e
KVM: x86: do not save guest-unsupported XSAVE state

commit 00c87e9a70a17b355b81c36adedf05e84f54e10d upstream.

Saving unsupported state prevents migration when the new host does not
support a XSAVE feature of the original host, even if the feature is not
exposed to the guest.

We've masked host features with guest-visible features before, with
4344ee981e21 ("KVM: x86: only copy XSAVE state for the supported
features") and dropped it when implementing XSAVES.  Do it again.

Fixes: df1daba7d1cb ("KVM: x86: support XSAVES usage in the host")
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/x86/kvm/x86.c