aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/fpga
diff options
context:
space:
mode:
authorVitaly Kuznetsov <[email protected]>2024-09-20 15:44:22 +0000
committerPaolo Bonzini <[email protected]>2024-10-20 16:10:27 +0000
commit9a400068a1586bc4f10ee8b0443527de27d8834c (patch)
treec5bda3c08283a5786f48b7fc7092aef58e6e98ab /drivers/fpga
parentKVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory (diff)
downloadkernel-9a400068a1586bc4f10ee8b0443527de27d8834c.tar.gz
kernel-9a400068a1586bc4f10ee8b0443527de27d8834c.zip
KVM: selftests: x86: Avoid using SSE/AVX instructions
Some distros switched gcc to '-march=x86-64-v3' by default and while it's hard to find a CPU which doesn't support it today, many KVM selftests fail with ==== Test Assertion Failure ==== lib/x86_64/processor.c:570: Unhandled exception in guest pid=72747 tid=72747 errno=4 - Interrupted system call Unhandled exception '0x6' at guest RIP '0x4104f7' The failure is easy to reproduce elsewhere with $ make clean && CFLAGS='-march=x86-64-v3' make -j && ./x86_64/kvm_pv_test The root cause of the problem seems to be that with '-march=x86-64-v3' GCC uses AVX* instructions (VMOVQ in the example above) and without prior XSETBV() in the guest this results in #UD. It is certainly possible to add it there, e.g. the following saves the day as well: Signed-off-by: Vitaly Kuznetsov <[email protected]> Message-ID: <[email protected]> Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'drivers/fpga')
0 files changed, 0 insertions, 0 deletions