diff options
| author | Sean Christopherson <[email protected]> | 2025-02-01 01:38:18 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-02-12 18:45:54 +0000 |
| commit | 4198f38aed24f8f4634867f640cc60c65789b4ec (patch) | |
| tree | fc93200d6dc3beac54ae8c3059249614006e9337 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | KVM: x86: Don't take kvm->lock when iterating over vCPUs in suspend notifier (diff) | |
| download | kernel-4198f38aed24f8f4634867f640cc60c65789b4ec.tar.gz kernel-4198f38aed24f8f4634867f640cc60c65789b4ec.zip | |
KVM: x86: Eliminate "handling" of impossible errors during SUSPEND
Drop KVM's handling of kvm_set_guest_paused() failure when reacting to a
SUSPEND notification, as kvm_set_guest_paused() only "fails" if the vCPU
isn't using kvmclock, and KVM's notifier callback pre-checks that kvmclock
is active. I.e. barring some bizarre edge case that shouldn't be treated
as an error in the first place, kvm_arch_suspend_notifier() can't fail.
Reviewed-by: Paul Durrant <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions