67f3da9d74
There is nothing inherently architecture specific about the memory test although we may have to manage different restrictions of unaligned access across architectures. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> |
||
---|---|---|
.. | ||
system | ||
hello-i386.c | ||
Makefile.include | ||
Makefile.softmmu-target | ||
Makefile.target | ||
README | ||
test-i386-code16.S | ||
test-i386-fprem.c | ||
test-i386-muldiv.h | ||
test-i386-shift.h | ||
test-i386-ssse3.c | ||
test-i386-vm86.S | ||
test-i386.c | ||
test-i386.h |
These are i386 specific guest programs test-i386 --------- This program executes most of the 16 bit and 32 bit x86 instructions and generates a text output, for comparison with the output obtained with a real CPU or another emulator. The Linux system call modify_ldt() is used to create x86 selectors to test some 16 bit addressing and 32 bit with segmentation cases. The Linux system call vm86() is used to test vm86 emulation. Various exceptions are raised to test most of the x86 user space exception reporting. linux-test ---------- This program tests various Linux system calls. It is used to verify that the system call parameters are correctly converted between target and host CPUs. test-i386-fprem --------------- test-mmap --------- sha1 ---- hello-i386 ----------