Searched hist:"187 c8833def8a191c7f01d7932eac1bd2ab84af1" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/arch/x86/kvm/ |
| H A D | hyperv.c | diff 187c8833def8a191c7f01d7932eac1bd2ab84af1 Thu Oct 21 19:49:27 CDT 2021 Sean Christopherson <seanjc@google.com> KVM: x86: Use rw_semaphore for APICv lock to allow vCPU parallelism
Use a rw_semaphore instead of a mutex to coordinate APICv updates so that
vCPUs responding to requests can take the lock for read and run in
parallel. Using a mutex forces serialization of vCPUs even though
kvm_vcpu_update_apicv() only touches data local to that vCPU or is
protected by a different lock, e.g. SVM's ir_list_lock.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211022004927.1448382-5-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
| H A D | x86.c | diff 187c8833def8a191c7f01d7932eac1bd2ab84af1 Thu Oct 21 19:49:27 CDT 2021 Sean Christopherson <seanjc@google.com> KVM: x86: Use rw_semaphore for APICv lock to allow vCPU parallelism
Use a rw_semaphore instead of a mutex to coordinate APICv updates so that
vCPUs responding to requests can take the lock for read and run in
parallel. Using a mutex forces serialization of vCPUs even though
kvm_vcpu_update_apicv() only touches data local to that vCPU or is
protected by a different lock, e.g. SVM's ir_list_lock.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211022004927.1448382-5-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | kvm_host.h | diff 187c8833def8a191c7f01d7932eac1bd2ab84af1 Thu Oct 21 19:49:27 CDT 2021 Sean Christopherson <seanjc@google.com> KVM: x86: Use rw_semaphore for APICv lock to allow vCPU parallelism
Use a rw_semaphore instead of a mutex to coordinate APICv updates so that
vCPUs responding to requests can take the lock for read and run in
parallel. Using a mutex forces serialization of vCPUs even though
kvm_vcpu_update_apicv() only touches data local to that vCPU or is
protected by a different lock, e.g. SVM's ir_list_lock.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211022004927.1448382-5-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|