From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v3 1/1] s390x: verify EQBS/SQBS is unavailable
Date: Wed, 3 Aug 2022 15:58:51 +0200 [thread overview]
Message-ID: <20220803135851.384805-2-nrb@linux.ibm.com> (raw)
In-Reply-To: <20220803135851.384805-1-nrb@linux.ibm.com>
QEMU doesn't provide EQBS/SQBS instructions, so we should check they
result in an exception.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
---
s390x/intercept.c | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/s390x/intercept.c b/s390x/intercept.c
index 9e826b6c79ad..48eb2d22a2cc 100644
--- a/s390x/intercept.c
+++ b/s390x/intercept.c
@@ -197,6 +197,34 @@ static void test_diag318(void)
}
+static void test_qbs(void)
+{
+ report_prefix_push("qbs");
+ if (!host_is_qemu()) {
+ report_skip("QEMU-only test");
+ report_prefix_pop();
+ return;
+ }
+
+ report_prefix_push("sqbs");
+ expect_pgm_int();
+ asm volatile(
+ " .insn rsy,0xeb000000008a,0,0,0(0)\n"
+ : : : "memory", "cc");
+ check_pgm_int_code(PGM_INT_CODE_OPERATION);
+ report_prefix_pop();
+
+ report_prefix_push("eqbs");
+ expect_pgm_int();
+ asm volatile(
+ " .insn rrf,0xb99c0000,0,0,0,0\n"
+ : : : "memory", "cc");
+ check_pgm_int_code(PGM_INT_CODE_OPERATION);
+ report_prefix_pop();
+
+ report_prefix_pop();
+}
+
struct {
const char *name;
void (*func)(void);
@@ -208,6 +236,7 @@ struct {
{ "stidp", test_stidp, false },
{ "testblock", test_testblock, false },
{ "diag318", test_diag318, false },
+ { "qbs", test_qbs, false },
{ NULL, NULL, false }
};
--
2.36.1
next prev parent reply other threads:[~2022-08-03 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 13:58 [kvm-unit-tests PATCH v3 0/1] s390x: verify EQBS/SQBS is unavailable Nico Boehr
2022-08-03 13:58 ` Nico Boehr [this message]
2022-08-03 17:23 ` [kvm-unit-tests PATCH v3 1/1] " Claudio Imbrenda
2022-08-03 22:17 ` Thomas Huth
2022-08-09 6:20 ` Nico Boehr
2022-08-24 7:40 ` Janosch Frank
2022-08-24 8:31 ` Thomas Huth
2022-09-08 12:43 ` Christian Borntraeger
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=20220803135851.384805-2-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@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