mirror of https://gitlab.com/qemu-project/qemu
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
![]() Currently the boot.S code assumes everything starts at EL1. This will break things like the memory test which will barf on unaligned memory access when run at a higher level. Adapt the boot code to do some basic verification of the starting mode and the minimal configuration to move to the lower exception levels. With this we can run the memory test with: -M virt,secure=on -M virt,secure=on,virtualization=on -M virt,virtualisation=on If a test needs to be at a particular EL it can use the semihosting command line to indicate the level we should execute in. Cc: Julian Armistead <julian.armistead@linaro.org> Cc: Jim MacArthur <jim.macarthur@linaro.org> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-ID: <20250603110204.838117-4-alex.bennee@linaro.org> |
12 hours ago | |
---|---|---|
.. | ||
aarch64 | 12 hours ago | |
aarch64_be | 8 months ago | |
alpha | 9 months ago | |
arm | 3 months ago | |
hexagon | 3 months ago | |
hppa | 1 year ago | |
i386 | 3 months ago | |
loongarch64 | 1 month ago | |
m68k | 1 year ago | |
minilib | 11 months ago | |
mips | 2 years ago | |
multiarch | 3 months ago | |
openrisc | ||
plugins | 1 month ago | |
ppc64 | 7 months ago | |
ppc64le | 3 years ago | |
riscv64 | 10 months ago | |
s390x | 4 months ago | |
sh4 | 1 year ago | |
tricore | 2 years ago | |
x86_64 | 2 days ago | |
xtensa | 1 year ago | |
xtensaeb | 2 years ago | |
Makefile.target | 7 months ago | |
README | 10 months ago |
README
This directory contains various interesting guest binaries for regression testing the Tiny Code Generator doing system and user-mode emulation. The multiarch directory contains shared code for tests that can be built for all guest architectures. Architecture specific code can be found in their respective directories. System mode tests will be under the "system" subdirectories. GDB scripts for exercising the gdbstub on specific tests will be found under the "gdbstb" subdirectories. See the developer guide for more instructions on "make check-tcg"