qemu-e2k/tests
Paolo Bonzini e7bbb7cb71 target/i386: introduce flags writeback mechanism
ALU instructions can write to both memory and flags.  If the CC_SRC*
and CC_DST locations have been written already when a memory access
causes a fault, the value in CC_SRC* and CC_DST might be interpreted
with the wrong CC_OP (the one that is in effect before the instruction.

Besides just using the wrong result for the flags, something like
subtracting -1 can have disastrous effects if the current CC_OP is
CC_OP_EFLAGS: this is because QEMU does not expect bits outside the ALU
flags to be set in CC_SRC, and env->eflags can end up set to all-ones.
In the case of the attached testcase, this sets IOPL to 3 and would
cause an assertion failure if SUB is moved to the new decoder.

This mechanism is not really needed for BMI instructions, which can
only write to a register, but put it to use anyway for cleanliness.
In the case of BZHI, the code has to be modified slightly to ensure
that decode->cc_src is written, otherwise the new assertions trigger.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2023-12-29 22:04:30 +01:00
..
avocado
bench
data
decode
docker
fp
guest-debug
image-fuzzer
include
keys
lcitool
migration
multiboot
perf/block/qcow2
plugin
qapi-schema
qemu-iotests
qtest
rocker
tcg target/i386: introduce flags writeback mechanism 2023-12-29 22:04:30 +01:00
tsan
uefi-test-tools
unit
vm
vmstate-static-checker-data
dbus-vmstate-daemon.sh
Makefile.include
meson.build
test-qht-par.c
vhost-user-bridge.c