mirror of
https://github.com/torvalds/linux.git
synced 2026-11-07 06:17:02 +01:00
KVM: Fix comments that refer to the non-existent VCPU_RUN ioctl
Neither the VCPU_RUN in kvm_main.c nor the VCPU RUN in kvm_host.h names an ioctl that exists. The one that enters the guest is KVM_RUN, so refer to it by that name. Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev> Link: https://patch.msgid.link/20260915084441.3846947-2-fuad.tabba@linux.dev Signed-off-by: Marc Zyngier <maz@kernel.org>
This commit is contained in:
parent
356abf7ced
commit
8233000034
|
|
@ -562,7 +562,7 @@ static inline int kvm_vcpu_exiting_guest_mode(struct kvm_vcpu *vcpu)
|
|||
/*
|
||||
* The memory barrier ensures a previous write to vcpu->requests cannot
|
||||
* be reordered with the read of vcpu->mode. It pairs with the general
|
||||
* memory barrier following the write of vcpu->mode in VCPU RUN.
|
||||
* memory barrier following the write of vcpu->mode in KVM_RUN.
|
||||
*/
|
||||
smp_mb__before_atomic();
|
||||
return cmpxchg(&vcpu->mode, IN_GUEST_MODE, EXITING_GUEST_MODE);
|
||||
|
|
|
|||
|
|
@ -470,7 +470,7 @@ static void kvm_vcpu_destroy(struct kvm_vcpu *vcpu)
|
|||
kvm_dirty_ring_free(&vcpu->dirty_ring);
|
||||
|
||||
/*
|
||||
* No need for rcu_read_lock as VCPU_RUN is the only place that changes
|
||||
* No need for rcu_read_lock as KVM_RUN is the only place that changes
|
||||
* the vcpu->pid pointer, and at destruction time all file descriptors
|
||||
* are already gone.
|
||||
*/
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user