Searched hist:a6b7e459ff6d569227980f711664f927100c73a8 (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/arch/s390/kvm/ |
H A D | gaccess.c | diff a6b7e459ff6d569227980f711664f927100c73a8 Wed Oct 01 07:48:42 CDT 2014 Thomas Huth <thuth@linux.vnet.ibm.com> KVM: s390: Make the simple ipte mutex specific to a VM instead of global
The ipte-locking should be done for each VM seperately, not globally. This way we avoid possible congestions when the simple ipte-lock is used and multiple VMs are running.
Suggested-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|
H A D | kvm-s390.c | diff a6b7e459ff6d569227980f711664f927100c73a8 Wed Oct 01 07:48:42 CDT 2014 Thomas Huth <thuth@linux.vnet.ibm.com> KVM: s390: Make the simple ipte mutex specific to a VM instead of global
The ipte-locking should be done for each VM seperately, not globally. This way we avoid possible congestions when the simple ipte-lock is used and multiple VMs are running.
Suggested-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|
/openbmc/linux/arch/s390/include/asm/ |
H A D | kvm_host.h | diff a6b7e459ff6d569227980f711664f927100c73a8 Wed Oct 01 07:48:42 CDT 2014 Thomas Huth <thuth@linux.vnet.ibm.com> KVM: s390: Make the simple ipte mutex specific to a VM instead of global
The ipte-locking should be done for each VM seperately, not globally. This way we avoid possible congestions when the simple ipte-lock is used and multiple VMs are running.
Suggested-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|