From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v3 0/5] s390x: More emulation tests
Date: Mon, 26 Aug 2019 18:34:57 +0200 [thread overview]
Message-ID: <20190826163502.1298-1-frankja@linux.ibm.com> (raw)
The first patch allows for CECSIM booting via PSW restart.
The other ones add diag288 and STSI tests, as well as diag308 subcode 0.
v3:
* Addressed review
* Added review-bys
v2:
* Tested under TCG
* Split out stsi into library
* Addressed review
Janosch Frank (5):
s390x: Support PSW restart boot
s390x: Diag288 test
s390x: Move stsi to library
s390x: STSI tests
s390x: Add diag308 subcode 0 testing
lib/s390x/asm/arch_def.h | 17 +++++
s390x/Makefile | 2 +
s390x/cstart64.S | 27 ++++++++
s390x/diag288.c | 130 +++++++++++++++++++++++++++++++++++++++
s390x/diag308.c | 31 +++-------
s390x/flat.lds | 14 +++--
s390x/skey.c | 18 ------
s390x/stsi.c | 84 +++++++++++++++++++++++++
s390x/unittests.cfg | 7 +++
9 files changed, 286 insertions(+), 44 deletions(-)
create mode 100644 s390x/diag288.c
create mode 100644 s390x/stsi.c
--
2.17.0
next reply other threads:[~2019-08-26 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 16:34 Janosch Frank [this message]
2019-08-26 16:34 ` [kvm-unit-tests PATCH v3 1/5] s390x: Support PSW restart boot Janosch Frank
2019-08-26 16:34 ` [kvm-unit-tests PATCH v3 2/5] s390x: Diag288 test Janosch Frank
2019-08-26 17:14 ` Thomas Huth
2019-08-27 7:46 ` [kvm-unit-tests PATCH] " Janosch Frank
2019-08-27 10:29 ` Thomas Huth
2019-08-26 16:35 ` [kvm-unit-tests PATCH v3 3/5] s390x: Move stsi to library Janosch Frank
2019-08-26 16:35 ` [kvm-unit-tests PATCH v3 4/5] s390x: STSI tests Janosch Frank
2019-08-30 12:07 ` David Hildenbrand
2019-09-03 10:53 ` Janosch Frank
2019-09-03 10:57 ` David Hildenbrand
2019-09-03 10:58 ` Thomas Huth
2019-08-26 16:35 ` [kvm-unit-tests PATCH v3 5/5] s390x: Add diag308 subcode 0 testing Janosch Frank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190826163502.1298-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).