summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@ozlabs.org>2017-09-11 09:05:30 +0300
committerPaul Mackerras <paulus@ozlabs.org>2017-09-12 09:02:27 +0300
commitcf5f6f3125241853462334b1bc696f3c3c492178 (patch)
tree4108b0c8c4d6bab9772d8ff03f20461aa1887385 /tools/perf/scripts/python/syscall-counts.py
parentd222af072380c4470295c07d84ecb15f4937e365 (diff)
downloadlinux-cf5f6f3125241853462334b1bc696f3c3c492178.tar.xz
KVM: PPC: Book3S HV: Hold kvm->lock around call to kvmppc_update_lpcr
Commit 468808bd35c4 ("KVM: PPC: Book3S HV: Set process table for HPT guests on POWER9", 2017-01-30) added a call to kvmppc_update_lpcr() which doesn't hold the kvm->lock mutex around the call, as required. This adds the lock/unlock pair, and for good measure, includes the kvmppc_setup_partition_table() call in the locked region, since it is altering global state of the VM. This error appears not to have any fatal consequences for the host; the consequences would be that the VCPUs could end up running with different LPCR values, or an update to the LPCR value by userspace using the one_reg interface could get overwritten, or the update done by kvmhv_configure_mmu() could get overwritten. Cc: stable@vger.kernel.org # v4.10+ Fixes: 468808bd35c4 ("KVM: PPC: Book3S HV: Set process table for HPT guests on POWER9") Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions