summaryrefslogtreecommitdiff
path: root/arch/s390/kvm/sthyi.c
diff options
context:
space:
mode:
authorChristian Borntraeger <borntraeger@de.ibm.com>2017-02-27 21:14:47 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2017-03-16 13:04:38 +0100
commitc0a6bfdc18b83290b65372a7687134052f382bdf (patch)
tree83f8158c5bede6e720c2dac1af5d834b2ac31281 /arch/s390/kvm/sthyi.c
parent4d5f2c04c8a462a1c7ad3fdc138515c84fa65379 (diff)
KVM: s390: Handle sthyi also for instruction intercept
Right now we handle the STHYI only via the operation exception intercept (illegal instruction). If hardware ever decides to provide an instruction intercept for STHYI, we should handle that as well. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'arch/s390/kvm/sthyi.c')
-rw-r--r--arch/s390/kvm/sthyi.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/arch/s390/kvm/sthyi.c b/arch/s390/kvm/sthyi.c
index 05c98bb853cf..926b5244263e 100644
--- a/arch/s390/kvm/sthyi.c
+++ b/arch/s390/kvm/sthyi.c
@@ -404,6 +404,9 @@ int handle_sthyi(struct kvm_vcpu *vcpu)
u64 code, addr, cc = 0;
struct sthyi_sctns *sctns = NULL;
+ if (!test_kvm_facility(vcpu->kvm, 74))
+ return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
+
/*
* STHYI requires extensive locking in the higher hypervisors
* and is very computational/memory expensive. Therefore we