OSDN Git Service

s390: vsie: Use effective CRYCBD.31 to check CRYCBD validity
authorPierre Morel <pmorel@linux.ibm.com>
Mon, 11 Feb 2019 09:20:49 +0000 (10:20 +0100)
committerChristian Borntraeger <borntraeger@de.ibm.com>
Mon, 11 Feb 2019 12:19:20 +0000 (13:19 +0100)
commitb10bd9a256aec504c14a7c9b6fccb6301ecf290a
treeca2c0bbc5b1750d152e64314ecc46e47142a1aa7
parentbfeffd155283772bbe78c6a05dec7c0128ee500c
s390: vsie: Use effective CRYCBD.31 to check CRYCBD validity

When facility.76 MSAX3 is present for the guest we must issue a validity
interception if the CRYCBD is not valid.

The bit CRYCBD.31 is an effective field and tested at each guest level
and has for effect to mask the facility.76

It follows that if CRYCBD.31 is clear and AP is not in use  we do not
have to test the CRYCBD validatity even if facility.76 is present in the
host.

Fixes: 6ee74098201b ("KVM: s390: vsie: allow CRYCB FORMAT-0")
Cc: stable@vger.kernel.org
Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
Reported-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Acked-by: David Hildenbrand <david@redhat.com>
Acked-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <1549876849-32680-1-git-send-email-pmorel@linux.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
arch/s390/kvm/vsie.c