diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-07-03 07:04:21 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-07-03 19:16:28 +0300 |
| commit | 7c83d096aed055a7763a03384f92115363448b71 (patch) | |
| tree | cbef83178dccda56bce36c2387959803ed8275d4 /tools/perf/scripts/python | |
| parent | d74fcfc1f0ff4b6c26ecef1f9e48d8089ab4eaac (diff) | |
| download | linux-7c83d096aed055a7763a03384f92115363448b71.tar.xz | |
KVM: x86: Mark CR4.TSD as being possibly owned by the guest
Mark CR4.TSD as being possibly owned by the guest as that is indeed the
case on VMX. Without TSD being tagged as possibly owned by the guest, a
targeted read of CR4 to get TSD could observe a stale value. This bug
is benign in the current code base as the sole consumer of TSD is the
emulator (for RDTSC) and the emulator always "reads" the entirety of CR4
when grabbing bits.
Add a build-time assertion in to ensure VMX doesn't hand over more CR4
bits without also updating x86.
Fixes: 52ce3c21aec3 ("x86,kvm,vmx: Don't trap writes to CR4.TSD")
Cc: stable@vger.kernel.org
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200703040422.31536-2-sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions