diff options
Diffstat (limited to 'results/classifier/105/instruction/1699567')
| -rw-r--r-- | results/classifier/105/instruction/1699567 | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/results/classifier/105/instruction/1699567 b/results/classifier/105/instruction/1699567 new file mode 100644 index 00000000..3b94c0ea --- /dev/null +++ b/results/classifier/105/instruction/1699567 @@ -0,0 +1,45 @@ +instruction: 0.841 +device: 0.765 +socket: 0.608 +mistranslation: 0.606 +other: 0.581 +semantic: 0.565 +graphic: 0.530 +vnc: 0.506 +network: 0.461 +assembly: 0.460 +boot: 0.421 +KVM: 0.160 + +Qemu does not force SSE data alignment + +I have an OS that tries to use SSE operations. It works fine in qemu. But it crashes when I try to run the OS at the host cpu using KVM. + +The instruction that crahes with #GP(0) is + movaps ADDR,%xmm0 + +The documentation says ADDR has to be 16-bytes alignment otherwise #GP is generated. And indeed the problem was with the data alignment. After adjusting it at my side the OS works fine both with Qemu and KVM. + +It would be great if QEMU followed specification more closely and forced SSE data alignment requirements. It will help to catch alignment issues early and debug it easier. + + +$ qemu-system-x86_64 -version +QEMU emulator version 2.9.50 (v2.9.0-1363-g95eef1c68b) +Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers + +The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. +If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience. + +I am currently running into this bug on QEMU emulator version 5.1.0. +movaps unaligned access works fine in qemu, when it should throw a GP. Likewise, the same code on physical hardware throws a GP. + +Yep. Long-standing bug. + + +This is an automated cleanup. This bug report has been moved to QEMU's +new bug tracker on gitlab.com and thus gets marked as 'expired' now. +Please continue with the discussion here: + + https://gitlab.com/qemu-project/qemu/-/issues/217 + + |