On Fri, 2021-08-06 at 07:25 +0200, Thomas Huth wrote: > On 05/08/2021 00.51, 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 <i...@linux.ibm.com> > > --- > > > > v7: > > https://lists.nongnu.org/archive/html/qemu-devel/2021-08/msg00463.html > > v7 -> v8: Another rebase needed due to the conflict with Jonathan's > > 50e36dd61652. > > Thanks for respinning this patch! I now gave it a try, and it seems > to work, > but the output looks a little funny: > > SKIPPED signals on s390x because BROKEN awaiting sigframe clean- > ups and > vdso support > TEST test-mmap (default) on s390x > TEST testthread on s390x > TEST threadcount on s390x > TEST hello-s390x on s390x > TEST csst on s390x > TEST ipm on s390x > TEST exrl-trt on s390x > TEST exrl-trtr on s390x > TEST pack on s390x > TEST mvo on s390x > TEST mvc on s390x > TEST trap on s390x > TEST signals-s390x on s390x > > i.e. it first says "SKIPPED signals", but later still executes the > test. > Could that be fixed somehow?
These are two different tests actually. signals is a multiarch test that is valid on other machines as well. The new signals-s390x tests only s390x-specific aspects of signal handling. Best regards, Ilya