diff options
| author | Binbin Wu <[email protected]> | 2025-02-22 01:42:18 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2025-03-14 18:20:54 +0000 |
| commit | 44428e4936022a7a31743017849b167e64f33a32 (patch) | |
| tree | ce208f8baea8e5ce8072f559f508e333dec5041d /rust/helpers/workqueue.c | |
| parent | KVM: x86: Have ____kvm_emulate_hypercall() read the GPRs (diff) | |
| download | kernel-44428e4936022a7a31743017849b167e64f33a32.tar.gz kernel-44428e4936022a7a31743017849b167e64f33a32.zip | |
KVM: x86: Move pv_unhalted check out of kvm_vcpu_has_events()
Move pv_unhalted check out of kvm_vcpu_has_events(), check pv_unhalted
explicitly when handling PV unhalt and expose kvm_vcpu_has_events().
kvm_vcpu_has_events() returns true if pv_unhalted is set, and pv_unhalted
is only cleared on transitions to KVM_MP_STATE_RUNNABLE. If the guest
initiates a spurious wakeup, pv_unhalted could be left set in perpetuity.
Currently, this is not problematic because kvm_vcpu_has_events() is only
called when handling PV unhalt. However, if kvm_vcpu_has_events() is used
for other purposes in the future, it could return the unexpected results.
Export kvm_vcpu_has_events() for its usage in broader contexts.
Suggested-by: Sean Christopherson <[email protected]>
Signed-off-by: Binbin Wu <[email protected]>
Message-ID: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'rust/helpers/workqueue.c')
0 files changed, 0 insertions, 0 deletions