diff options
| author |   Sean Christopherson <seanjc@google.com> | 2025-02-24 15:55:41 -0800 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2025-02-26 13:17:23 -0500 |
| commit | fd21732682e20f1eefe73abbf6fc866b6bc51e9e (patch) | |
| tree | 89b69d4130b0fa1d7d51865b1527bca64dad4d02 /scripts/lib/kdoc/kdoc_files.py | |
| parent | KVM: x86: Unload MMUs during vCPU destruction, not before (diff) | |
| download | linux-rng-fd21732682e20f1eefe73abbf6fc866b6bc51e9e.tar.xz linux-rng-fd21732682e20f1eefe73abbf6fc866b6bc51e9e.zip | |
KVM: x86: Fold guts of kvm_arch_sync_events() into kvm_arch_pre_destroy_vm()
Fold the guts of kvm_arch_sync_events() into kvm_arch_pre_destroy_vm(), as
the kvmclock and PIT background workers only need to be stopped before
destroying vCPUs (to avoid accessing vCPUs as they are being freed); it's
a-ok for them to be running while the VM is visible on the global vm_list.
Note, the PIT also needs to be stopped before IRQ routing is freed
(because KVM's IRQ routing is garbage and assumes there is always non-NULL
routing).
Opportunistically add comments to explain why KVM stops/frees certain
assets early.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20250224235542.2562848-7-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions