David Hildenbrand 4215825eeb KVM: s390: don't switch to ESCA for ucontrol ... sca_add_vpcu is not called for ucontrol guests. We must also not apply the sca checking for sca_can_add_vcpu as ucontrol guests do not have to follow the sca limits. As common code already checks that id < KVM_MAX_VCPUS all other data structures are safe as well. Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>		2015-11-30 12:47:11 +01:00
..
diag.c	KVM: Use common function for VCPU lookup by id	2015-11-30 12:47:04 +01:00
gaccess.c	KVM: s390: Introduce switching code	2015-11-30 12:47:08 +01:00
gaccess.h
guestdbg.c	KVM: s390: filter space-switch events when PER is enforced	2015-07-29 10:36:22 +02:00
intercept.c	KVM: s390: rewrite vcpu_post_run and drop out early	2015-11-30 12:47:05 +01:00
interrupt.c	KVM: s390: fast path for sca_ext_call_pending	2015-11-30 12:47:09 +01:00
irq.h
Kconfig
kvm-s390.c	KVM: s390: don't switch to ESCA for ucontrol	2015-11-30 12:47:11 +01:00
kvm-s390.h	KVM: s390: Introduce new structures	2015-11-30 12:47:07 +01:00
Makefile
priv.c	KVM: s390: fix pfmf intercept handler	2015-11-19 11:08:17 +01:00
sigp.c	KVM: s390: fix wrong lookup of VCPUs by array index	2015-11-19 14:47:43 +01:00
trace-s390.h	KVM: s390: more irq names for trace events	2015-07-29 11:02:34 +02:00
trace.h