diff options
author | Yu Zhang <yu.c.zhang@linux.intel.com> | 2019-02-01 00:09:23 +0800 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-02-22 19:25:10 +0100 |
commit | de3ccd26fafc707b09792d9b633c8b5b48865315 (patch) | |
tree | 0a8d3d19ab24b7accfe02d160445688224fa238d /Makefile | |
parent | 511da98d207d5c0675a10351b01e37cbe50a79e5 (diff) | |
download | linux-de3ccd26fafc707b09792d9b633c8b5b48865315.tar.gz linux-de3ccd26fafc707b09792d9b633c8b5b48865315.tar.bz2 linux-de3ccd26fafc707b09792d9b633c8b5b48865315.zip |
KVM: MMU: record maximum physical address width in kvm_mmu_extended_role
Previously, commit 7dcd57552008 ("x86/kvm/mmu: check if tdp/shadow
MMU reconfiguration is needed") offered some optimization to avoid
the unnecessary reconfiguration. Yet one scenario is broken - when
cpuid changes VM's maximum physical address width, reconfiguration
is needed to reset the reserved bits. Also, the TDP may need to
reset its shadow_root_level when this value is changed.
To fix this, a new field, maxphyaddr, is introduced in the extended
role structure to keep track of the configured guest physical address
width.
Signed-off-by: Yu Zhang <yu.c.zhang@linux.intel.com>
Cc: stable@vger.kernel.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions