diff options
author | Isaku Yamahata <[email protected]> | 2022-11-30 23:09:29 +0000 |
---|---|---|
committer | Paolo Bonzini <[email protected]> | 2022-12-29 15:48:34 -0500 |
commit | 667a83bf6a30b5660d02712dce9fb07e99abde38 (patch) | |
tree | 7f213e7d16f3983acda38553a0192155c9fce731 /tools/perf/scripts/python/stackcollapse.py | |
parent | 0bf50497f03b3d892c470c7d1a10a3e9c3c95821 (diff) |
KVM: Remove on_each_cpu(hardware_disable_nolock) in kvm_exit()
Drop the superfluous invocation of hardware_disable_nolock() during
kvm_exit(), as it's nothing more than a glorified nop.
KVM automatically disables hardware on all CPUs when the last VM is
destroyed, and kvm_exit() cannot be called until the last VM goes
away as the calling module is pinned by an elevated refcount of the fops
associated with /dev/kvm. This holds true even on x86, where the caller
of kvm_exit() is not kvm.ko, but is instead a dependent module, kvm_amd.ko
or kvm_intel.ko, as kvm_chardev_ops.owner is set to the module that calls
kvm_init(), not hardcoded to the base kvm.ko module.
Signed-off-by: Isaku Yamahata <[email protected]>
[sean: rework changelog]
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/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions