summaryrefslogtreecommitdiff
path: root/arch/x86/kvm/mmu.c
diff options
context:
space:
mode:
authorSebastian Andrzej Siewior <bigeasy@linutronix.de>2019-09-25 23:37:21 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2019-09-26 13:20:55 +0200
commit504ce1954fba888936c9d13ccc1e3db9b8f613d5 (patch)
treedb518fe49d637b5730ba70f41bb1e28af3e415bc /arch/x86/kvm/mmu.c
parent40bc47b08b6efc8b64fef77cb46974f634215425 (diff)
KVM: x86: Expose XSAVEERPTR to the guest
I was surprised to see that the guest reported `fxsave_leak' while the host did not. After digging deeper I noticed that the bits are simply masked out during enumeration. The XSAVEERPTR feature is actually a bug fix on AMD which means the kernel can disable a workaround. Pass XSAVEERPTR to the guest if available on the host. Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/mmu.c')
0 files changed, 0 insertions, 0 deletions