diff options
| author |   Sean Christopherson <seanjc@google.com> | 2021-10-08 19:12:11 -0700 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2021-12-08 04:24:53 -0500 |
| commit | cdafece4b964a27b2d3d76bf5725b49415bbaaea (patch) | |
| tree | 95d6d88780e935684554d9044efe78242df07d66 /virt | |
| parent | KVM: x86: Directly block (instead of "halting") UNINITIALIZED vCPUs (diff) | |
| download | linux-dev-cdafece4b964a27b2d3d76bf5725b49415bbaaea.tar.xz linux-dev-cdafece4b964a27b2d3d76bf5725b49415bbaaea.zip | |
KVM: x86: Invoke kvm_vcpu_block() directly for non-HALTED wait states
Call kvm_vcpu_block() directly for all wait states except HALTED so that
kvm_vcpu_halt() is no longer a misnomer on x86.
Functionally, this means KVM will never attempt halt-polling or adjust
vcpu->halt_poll_ns for INIT_RECEIVED (a.k.a. Wait-For-SIPI (WFS)) or
AP_RESET_HOLD; UNINITIALIZED is handled in kvm_arch_vcpu_ioctl_run(),
and x86 doesn't use any other "wait" states.
As mentioned above, the motivation of this is purely so that "halt" isn't
overloaded on x86, e.g. in KVM's stats. Skipping halt-polling for WFS
(and RESET_HOLD) has no meaningful effect on guest performance as there
are typically single-digit numbers of INIT-SIPI sequences per AP vCPU,
per boot, versus thousands of HLTs just to boot to console.
Reviewed-by: David Matlack <dmatlack@google.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211009021236.4122790-19-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions