QEMU suports a guest state "guest-panicked" which indicates something in the guest went wrong, for example on s390x, when an external interrupt loop was triggered. Since the guest does not continue to run when it is in the guest-panicked state, it is currently impossible to write panicking tests in kvm-unit-tests. Support from the runtime is needed to check that the guest enters the guest-panicked state. This series adds the required support to the runtime together with two tests for s390x which cause guest panics. Nico Boehr (3): runtime: add support for panic tests s390x: add extint loop test s390x: add pgm spec interrupt loop test s390x/Makefile | 2 ++ s390x/extint-loop.c | 64 +++++++++++++++++++++++++++++++++++++++++++ s390x/pgmint-loop.c | 46 +++++++++++++++++++++++++++++++ s390x/run | 2 +- s390x/unittests.cfg | 8 ++++++ scripts/arch-run.bash | 47 +++++++++++++++++++++++++++++++ scripts/runtime.bash | 3 ++ 7 files changed, 171 insertions(+), 1 deletion(-) create mode 100644 s390x/extint-loop.c create mode 100644 s390x/pgmint-loop.c -- 2.36.1
