summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorChristian Borntraeger <borntraeger@de.ibm.com>2014-08-05 16:44:14 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2014-12-04 15:29:13 +0100
commit7a72f7a140bfd3a5dae73088947010bfdbcf6a40 (patch)
treebb6f945f4460a39e7d0e6b242ecf656508891c27 /kernel
parenteed6e79d7362335967def243cc891179a9c59892 (diff)
downloadop-kernel-dev-7a72f7a140bfd3a5dae73088947010bfdbcf6a40.zip
op-kernel-dev-7a72f7a140bfd3a5dae73088947010bfdbcf6a40.tar.gz
KVM: track pid for VCPU only on KVM_RUN ioctl
We currently track the pid of the task that runs the VCPU in vcpu_load. If a yield to that VCPU is triggered while the PID of the wrong thread is active, the wrong thread might receive a yield, but this will most likely not help the executing thread at all. Instead, if we only track the pid on the KVM_RUN ioctl, there are two possibilities: 1) the thread that did a non-KVM_RUN ioctl is holding a mutex that the VCPU thread is waiting for. In this case, the VCPU thread is not runnable, but we also do not do a wrong yield. 2) the thread that did a non-KVM_RUN ioctl is sleeping, or doing something that does not block the VCPU thread. In this case, the VCPU thread can receive the directed yield correctly. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> CC: Rik van Riel <riel@redhat.com> CC: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com> CC: Michael Mueller <mimu@linux.vnet.ibm.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud