diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2014-02-27 22:54:11 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-03-03 12:49:42 +0100 |
| commit | ccf9844e5d99c1ee9a5b8c4f1332ac5211cbce03 (patch) | |
| tree | dee30cd06062315786557df30730a72eb5a32f3f /arch/x86/kvm/paging_tmpl.h | |
| parent | 684851a15744355f294ee3fee4ca2e9108382b47 (diff) | |
| download | blackbird-obmc-linux-ccf9844e5d99c1ee9a5b8c4f1332ac5211cbce03.tar.gz blackbird-obmc-linux-ccf9844e5d99c1ee9a5b8c4f1332ac5211cbce03.zip | |
kvm, vmx: Really fix lazy FPU on nested guest
Commit e504c9098ed6 (kvm, vmx: Fix lazy FPU on nested guest, 2013-11-13)
highlighted a real problem, but the fix was subtly wrong.
nested_read_cr0 is the CR0 as read by L2, but here we want to look at
the CR0 value reflecting L1's setup. In other words, L2 might think
that TS=0 (so nested_read_cr0 has the bit clear); but if L1 is actually
running it with TS=1, we should inject the fault into L1.
The effective value of CR0 in L2 is contained in vmcs12->guest_cr0, use
it.
Fixes: e504c9098ed6acd9e1079c5e10e4910724ad429f
Reported-by: Kashyap Chamarty <kchamart@redhat.com>
Reported-by: Stefan Bader <stefan.bader@canonical.com>
Tested-by: Kashyap Chamarty <kchamart@redhat.com>
Tested-by: Anthoine Bourgeois <bourgeois@bertin.fr>
Cc: stable@vger.kernel.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/paging_tmpl.h')
0 files changed, 0 insertions, 0 deletions
