Blame SOURCES/valgrind-3.14.0-s390x-vec-facility-bit.patch

7a6b42
commit 467c7c4c9665c0f8b41a4416722a027ebc05df2b
7a6b42
Author: Andreas Arnez <arnez@linux.ibm.com>
7a6b42
Date:   Mon Jan 21 14:10:00 2019 +0100
7a6b42
7a6b42
    Bug 403552 s390x: Fix vector facility bit number
7a6b42
    
7a6b42
    The wrong bit number was used when checking for the vector facility.  This
7a6b42
    can result in a fatal emulation error: "Encountered an instruction that
7a6b42
    requires the vector facility.  That facility is not available on this
7a6b42
    host."
7a6b42
    
7a6b42
    In many cases the wrong facility bit was usually set as well, hence
7a6b42
    nothing bad happened.  But when running Valgrind within a Qemu/KVM guest,
7a6b42
    the wrong bit was not (always?) set and the emulation error occurred.
7a6b42
    
7a6b42
    This fix simply corrects the vector facility bit number, changing it from
7a6b42
    128 to 129.
7a6b42
7a6b42
 
7a6b42
diff --git a/VEX/pub/libvex_s390x_common.h b/VEX/pub/libvex_s390x_common.h
7a6b42
index a8a66b96b..8723ee21d 100644
7a6b42
--- a/VEX/pub/libvex_s390x_common.h
7a6b42
+++ b/VEX/pub/libvex_s390x_common.h
7a6b42
@@ -103,7 +103,7 @@
7a6b42
 #define S390_FAC_MSA5    57  // message-security-assist 5
7a6b42
 #define S390_FAC_TREXE   73  // transactional execution
7a6b42
 #define S390_FAC_MSA4    77  // message-security-assist 4
7a6b42
-#define S390_FAC_VX      128 // vector facility
7a6b42
+#define S390_FAC_VX      129 // vector facility
7a6b42
 
7a6b42
 
7a6b42
 /*--------------------------------------------------------------*/