KVM: s390: vsie: support transactional execution
authorDavid Hildenbrand <dahi@linux.vnet.ibm.com>
Wed, 25 Nov 2015 10:13:32 +0000 (11:13 +0100)
committerChristian Borntraeger <borntraeger@de.ibm.com>
Tue, 21 Jun 2016 07:43:37 +0000 (09:43 +0200)
commit166ecb3d3cfecb62c31fdeab9949d70e84cd75cd
tree9cc1cce48f14d90406ac9e652aede6c6dc94ae23
parentbbeaa58b32ab627b68748543b3dcb98b9a28d570
KVM: s390: vsie: support transactional execution

As soon as guest 2 is allowed to use transactional execution (indicated via
STFLE), he can also enable it for guest 3.

Active transactional execution requires also the second prefix page to be
mapped. If that page cannot be mapped, a validity icpt has to be presented
to the guest.

We have to take care of tx being toggled on/off, otherwise we might get
wrong prefix validity icpt.

Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
arch/s390/kvm/vsie.c