diff options
| author | Sean Christopherson <seanjc@google.com> | 2021-09-20 17:02:57 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-09-30 04:27:06 -0400 |
| commit | 5ebbc470d7f33e8fba6bdb2ac8e62c49cec99108 (patch) | |
| tree | 2e1ebad87c23e83a8707fc4c35a63c6707ffdeb2 /tools/perf/scripts/python/flamegraph.py | |
| parent | KVM: x86: Do not mark all registers as avail/dirty during RESET/INIT (diff) | |
| download | linux-5ebbc470d7f33e8fba6bdb2ac8e62c49cec99108.tar.gz linux-5ebbc470d7f33e8fba6bdb2ac8e62c49cec99108.zip | |
KVM: x86: Remove defunct setting of CR0.ET for guests during vCPU create
Drop code to set CR0.ET for the guest during initialization of the guest
FPU. The code was added as a misguided bug fix by commit 380102c8e431
("KVM Set the ET flag in CR0 after initializing FX") to resolve an issue
where vcpu->cr0 (now vcpu->arch.cr0) was not correctly initialized on SVM
systems. While init_vmcb() did set CR0.ET, it only did so in the VMCB,
and subtly did not update vcpu->cr0. Stuffing CR0.ET worked around the
immediate problem, but did not fix the real bug of vcpu->cr0 and the VMCB
being out of sync. That underlying bug was eventually remedied by commit
18fa000ae453 ("KVM: SVM: Reset cr0 properly on vcpu reset").
No functional change intended.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20210921000303.400537-5-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions