summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorCédric Le Goater <clg@kaod.org>2019-05-24 15:20:30 +0200
committerPaul Mackerras <paulus@ozlabs.org>2019-05-30 05:53:33 +0200
commit7e10b9a6da619bcee243980d9c45112761a86e11 (patch)
tree59491b7497a405c12603e6b16a18dde174d36fa1 /include
parentKVM: PPC: Book3S HV: XIVE: Fix the enforced limit on the vCPU identifier (diff)
downloadlinux-7e10b9a6da619bcee243980d9c45112761a86e11.tar.xz
linux-7e10b9a6da619bcee243980d9c45112761a86e11.zip
KVM: PPC: Book3S HV: XIVE: Introduce a new mutex for the XIVE device
The XICS-on-XIVE KVM device needs to allocate XIVE event queues when a priority is used by the OS. This is referred as EQ provisioning and it is done under the hood when : 1. a CPU is hot-plugged in the VM 2. the "set-xive" is called at VM startup 3. sources are restored at VM restore The kvm->lock mutex is used to protect the different XIVE structures being modified but in some contexts, kvm->lock is taken under the vcpu->mutex which is not permitted by the KVM locking rules. Introduce a new mutex 'lock' for the KVM devices for them to synchronize accesses to the XIVE device structures. Reviewed-by: Greg Kurz <groug@kaod.org> Signed-off-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions