https://bugs.kde.org/show_bug.cgi?id=366413
--- Comment #3 from Zack Brdge <zbr...@gmail.com> --- Andreas: thank you for the reply. This was very helpful. As I expected, I've pushed my timeframe back a couple more months. I'm not actually sure how long it will take to complete this, but I'm adding some more information here for anyone else approaching this without much background on z/Architecture and/or Valgrind with respect to s390. Much of my time so far has just been spent getting up to speed on how to test these instructions, the issue being that some of the Linux distributions and emulators encountered don't actually support z13 instructions in question. I do not believe hercules 3.x nor hyperion (hercules 4.x) have integrated support for any of the new z13 instructions either yet, so that appears to be a path to avoid. In particular, as far as I'm aware, both of the newest RHEL and SUSE default distributions on IBM's LinuxONE system *do not yet support* z13. The version of SUSE I'm working with right now having uname: > Linux valgrindtest 3.12.59-60.45-default #1 SMP Sat Jun 25 06:19:03 UTC 2016 > (396c69d) s390x s390x s390x GNU/Linux Apparently, the 139 new vector instructions in z13 weren't added to the Linux Kernel until 3.18. Maybe this is different if running Ubuntu on IBM's cloud infrastructure. I haven't checked yet. My plan is just to compile a new kernel and try to reboot into it. So for example, the following test program will fail with an illegal instruction on the 3.12 kernel above. GCC 4.8 does not appear to support -march=z13, though binutils apparently does, so I built it with: "as -m64 -march=z13 test.S -o test.o && ld test.o -o test": > sys_exit=1 > .section .data > .section .text > .global _start > .section .bss > _start: > vgbm 16,0 # <-- fails here > la 1,sys_exit # exit syscall > la 2,0 # exit code should be 0 > svc 0 # call the kernel As for Valgrind, there are a couple files of immediate interest in the source tree and good starting points for working on this: 1) ./docs/internals/s390-opcodes.csv 2) ./include/vki/vki-s390x-linux.h Which should be pretty self explanatory. Hopefully, I'll have more time to update this with an actual patch soon as this is a fascinating platform. -- You are receiving this mail because: You are watching all bug changes.
