diff options
| author | Sean Christopherson <[email protected]> | 2021-07-13 09:32:54 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-08-02 11:01:52 -0400 |
| commit | f0428b3dcb2d7efe4b2a2304841645b48f0b6499 (patch) | |
| tree | 85b91cde8649a5bd067cce9c8e2dbd656e35a38e /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 503bc49424df4802ca34e4e1a024381fd7ced80e (diff) | |
KVM: VMX: Stuff vcpu->arch.apic_base directly at vCPU RESET
Write vcpu->arch.apic_base directly instead of bouncing through
kvm_set_apic_base(). This is a glorified nop, and is a step towards
cleaning up the mess that is local APIC creation.
When using an in-kernel APIC, kvm_create_lapic() explicitly sets
vcpu->arch.apic_base to MSR_IA32_APICBASE_ENABLE to avoid its own
kvm_lapic_set_base() call in kvm_lapic_reset() from triggering state
changes. That call during RESET exists purely to set apic->base_address
to the default base value. As a result, by the time VMX gets control,
the only missing piece is the BSP bit being set for the reset BSP.
For a userspace APIC, there are no side effects to process (for the APIC).
In both cases, the call to kvm_update_cpuid_runtime() is a nop because
the vCPU hasn't yet been exposed to userspace, i.e. there can't be any
CPUID entries.
No functional change intended.
Reviewed-by: Reiji Watanabe <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions