qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v6 2/2] tests/tcg/s390x: Test SIGILL and SIGSEGV handling


From: Thomas Huth
Subject: Re: [PATCH v6 2/2] tests/tcg/s390x: Test SIGILL and SIGSEGV handling
Date: Tue, 3 Aug 2021 16:33:30 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0

On 05/07/2021 23.04, Ilya Leoshkevich wrote:
Verify that s390x-specific uc_mcontext.psw.addr is reported correctly
and that signal handling interacts properly with debugging.

Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
---
  tests/tcg/s390x/Makefile.target               |  18 +-
  tests/tcg/s390x/gdbstub/test-signals-s390x.py |  76 ++++++++
  tests/tcg/s390x/signals-s390x.c               | 165 ++++++++++++++++++
  3 files changed, 258 insertions(+), 1 deletion(-)
  create mode 100644 tests/tcg/s390x/gdbstub/test-signals-s390x.py
  create mode 100644 tests/tcg/s390x/signals-s390x.c

diff --git a/tests/tcg/s390x/Makefile.target b/tests/tcg/s390x/Makefile.target
index 0036b8a505..0a5b25c156 100644
--- a/tests/tcg/s390x/Makefile.target
+++ b/tests/tcg/s390x/Makefile.target
@@ -1,4 +1,5 @@
-VPATH+=$(SRC_PATH)/tests/tcg/s390x
+S390X_SRC=$(SRC_PATH)/tests/tcg/s390x
+VPATH+=$(S390X_SRC)
  CFLAGS+=-march=zEC12 -m64
  TESTS+=hello-s390x
  TESTS+=csst
@@ -12,3 +13,18 @@ TESTS+=mvc
  # This triggers failures on s390x hosts about 4% of the time
  run-signals: signals
        $(call skip-test, $<, "BROKEN awaiting sigframe clean-ups")
+
+TESTS+=signals-s390x
+
+ifneq ($(HAVE_GDB_BIN),)
+GDB_SCRIPT=$(SRC_PATH)/tests/guest-debug/run-test.py
+
+run-gdbstub-signals-s390x: signals-s390x
+       $(call run-test, $@, $(GDB_SCRIPT) \
+               --gdb $(HAVE_GDB_BIN) \
+               --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
+               --bin $< --test $(S390X_SRC)/gdbstub/test-signals-s390x.py, \
+       "mixing signals and debugging on s390x")
+
+EXTRA_RUNS += run-gdbstub-signals-s390x
+endif

 Hi Ilya,

FYI, I've put patch 1/2 into a pull request today, but this testing patch has a non-trivial conflict with commit eba61056e4cc ... could you please check how to get this enabled properly again
and then respin this patch 2/2 here? Thanks!

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]