From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com,
david@redhat.com, farman@linux.ibm.com
Subject: [kvm-unit-tests PATCH v1 7/9] s390x: smp: add tests for CONDITIONAL EMERGENCY
Date: Mon, 21 Mar 2022 11:19:02 +0100 [thread overview]
Message-ID: <20220321101904.387640-8-nrb@linux.ibm.com> (raw)
In-Reply-To: <20220321101904.387640-1-nrb@linux.ibm.com>
Add a test for the conditional emergency signal.
We cover the following cases:
- invalid CPU address. Should lead to the order being rejected.
- the order is accepted and an emergency signal is delivered. We make sure
this is the case by disabling the CPU's PSW for IO interruptions.
Note we intentionally don't cover the case where the signal isn't
delivered. As per the PoP, implementations are allowed to make the signal
an unconditional one when the condition determination is precluded.
This test is unsupported under PV.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
---
s390x/smp.c | 43 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/s390x/smp.c b/s390x/smp.c
index 3bd7e7c8f5ed..9c4e27106aef 100644
--- a/s390x/smp.c
+++ b/s390x/smp.c
@@ -16,6 +16,7 @@
#include <asm/sigp.h>
#include <smp.h>
+#include <uv.h>
#include <gs.h>
#include <alloc_page.h>
@@ -604,6 +605,47 @@ static void test_emcall(void)
report_prefix_pop();
}
+static void test_cond_emcall(void)
+{
+ uint32_t status = 0;
+ struct psw psw;
+ int cc;
+ psw.mask = extract_psw_mask() & ~PSW_MASK_IO;
+ psw.addr = (unsigned long)emcall;
+
+ report_prefix_push("conditional emergency call");
+
+ if (uv_os_is_guest()) {
+ report_skip("unsupported under PV");
+ goto out;
+ }
+
+ report_prefix_push("invalid CPU address");
+
+ cc = sigp(INVALID_CPU_ADDRESS, SIGP_COND_EMERGENCY_SIGNAL, 0, NULL);
+ report(cc == 3, "CC = 3");
+
+ report_prefix_pop();
+
+ report_prefix_push("success");
+ set_flag(0);
+
+ smp_cpu_start(1, psw);
+ wait_for_flag();
+ set_flag(0);
+ cc = smp_sigp(1, SIGP_COND_EMERGENCY_SIGNAL, 0, &status);
+ report(!cc, "CC = 0");
+
+ wait_for_flag();
+ smp_cpu_stop(1);
+
+ report_prefix_pop();
+
+out:
+ report_prefix_pop();
+
+}
+
static void test_sense_running(void)
{
report_prefix_push("sense_running");
@@ -731,6 +773,7 @@ int main(void)
test_set_prefix();
test_ecall();
test_emcall();
+ test_cond_emcall();
test_sense_running();
test_reset();
test_reset_initial();
--
2.31.1
next prev parent reply other threads:[~2022-03-21 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:18 [kvm-unit-tests PATCH v1 0/9] s390x: Further extend instruction interception tests Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 1/9] s390x: smp: add tests for several invalid SIGP orders Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 2/9] s390x: smp: stop already stopped CPU Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 3/9] s390x: gs: move to new header file Nico Boehr
2022-03-21 10:18 ` [kvm-unit-tests PATCH v1 4/9] s390x: smp: add test for SIGP_STORE_ADTL_STATUS order Nico Boehr
2022-03-21 14:59 ` Claudio Imbrenda
2022-03-23 14:19 ` Nico Boehr
2022-03-23 15:47 ` Claudio Imbrenda
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 5/9] s390x: smp: add tests for SET_PREFIX Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 6/9] s390x: smp: add test for EMERGENCY_SIGNAL with invalid CPU address Nico Boehr
2022-03-21 10:19 ` Nico Boehr [this message]
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 8/9] s390x: add TPROT tests Nico Boehr
2022-03-21 10:19 ` [kvm-unit-tests PATCH v1 9/9] s390x: stsi: check zero and ignored bits in r0 and r1 Nico Boehr
2022-03-21 15:01 ` [kvm-unit-tests PATCH v1 0/9] s390x: Further extend instruction interception tests Claudio Imbrenda
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=20220321101904.387640-8-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.