From: Pierre Morel <pmorel@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
cohuck@redhat.com, imbrenda@linux.ibm.com, david@redhat.com,
nrb@linux.ibm.com, scgl@linux.ibm.com
Subject: [kvm-unit-tests PATCH v5 1/2] s390x: topology: Check the Perform Topology Function
Date: Mon, 24 Oct 2022 16:20:34 +0200 [thread overview]
Message-ID: <20221024142035.22668-2-pmorel@linux.ibm.com> (raw)
In-Reply-To: <20221024142035.22668-1-pmorel@linux.ibm.com>
We check the PTF instruction.
- We check polarization only for KVM.
- We do not expect KVM to support vertical polarization.
- We do not expect the Topology Change Report to be pending
or not at the moment the first PTF instruction with
PTF_CHECK function code is done as some code already did run
a polarization change may have occur.
Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
---
s390x/Makefile | 1 +
s390x/topology.c | 132 ++++++++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 3 +
3 files changed, 136 insertions(+)
create mode 100644 s390x/topology.c
diff --git a/s390x/Makefile b/s390x/Makefile
index bf1504f9..4b9a21a7 100644
--- a/s390x/Makefile
+++ b/s390x/Makefile
@@ -39,6 +39,7 @@ tests += $(TEST_DIR)/panic-loop-extint.elf
tests += $(TEST_DIR)/panic-loop-pgm.elf
tests += $(TEST_DIR)/migration-sck.elf
tests += $(TEST_DIR)/exittime.elf
+tests += $(TEST_DIR)/topology.elf
pv-tests += $(TEST_DIR)/pv-diags.elf
diff --git a/s390x/topology.c b/s390x/topology.c
new file mode 100644
index 00000000..ae146d16
--- /dev/null
+++ b/s390x/topology.c
@@ -0,0 +1,132 @@
+/* SPDX-License-Identifier: GPL-2.0-only */
+/*
+ * CPU Topology
+ *
+ * Copyright IBM Corp. 2022
+ *
+ * Authors:
+ * Pierre Morel <pmorel@linux.ibm.com>
+ */
+
+#include <libcflat.h>
+#include <asm/page.h>
+#include <asm/asm-offsets.h>
+#include <asm/interrupt.h>
+#include <asm/facility.h>
+#include <smp.h>
+#include <sclp.h>
+#include <s390x/vm.h>
+
+#define PTF_REQ_HORIZONTAL 0
+#define PTF_REQ_VERTICAL 1
+#define PTF_REQ_CHECK 2
+
+#define PTF_ERR_NO_REASON 0
+#define PTF_ERR_ALRDY_POLARIZED 1
+#define PTF_ERR_IN_PROGRESS 2
+
+static int ptf(unsigned long fc, unsigned long *rc)
+{
+ int cc;
+
+ asm volatile(
+ " .insn rre,0xb9a20000,%1,0\n"
+ " ipm %0\n"
+ " srl %0,28\n"
+ : "=d" (cc), "+d" (fc)
+ :
+ : "cc");
+
+ *rc = fc >> 8;
+ return cc;
+}
+
+static void test_ptf(void)
+{
+ unsigned long rc;
+ int cc;
+
+ /* PTF is a privilege instruction */
+ report_prefix_push("Privilege");
+ enter_pstate();
+ expect_pgm_int();
+ ptf(PTF_REQ_CHECK, &rc);
+ check_pgm_int_code(PGM_INT_CODE_PRIVILEGED_OPERATION);
+ report_prefix_pop();
+
+ report_prefix_push("Wrong fc");
+ expect_pgm_int();
+ ptf(0xff, &rc);
+ check_pgm_int_code(PGM_INT_CODE_SPECIFICATION);
+ report_prefix_pop();
+
+ report_prefix_push("Reserved bits");
+ expect_pgm_int();
+ ptf(0xffffffffffffff00UL, &rc);
+ check_pgm_int_code(PGM_INT_CODE_SPECIFICATION);
+ report_prefix_pop();
+
+ report_prefix_push("Topology Report pending");
+ /*
+ * At this moment the topology may already have changed
+ * since the VM has been started.
+ * However, we can test if a second PTF instruction
+ * reports that the topology did not change since the
+ * preceding PFT instruction.
+ */
+ ptf(PTF_REQ_CHECK, &rc);
+ cc = ptf(PTF_REQ_CHECK, &rc);
+ report(cc == 0, "PTF check should clear topology report");
+ report_prefix_pop();
+
+ report_prefix_push("Topology polarisation check");
+ /*
+ * We can not assume the state of the polarization for
+ * any Virtual Machine but KVM.
+ * Let's skip the polarisation tests for other VMs.
+ */
+ if (!vm_is_kvm()) {
+ report_skip("Topology polarisation check is done for KVM only");
+ goto end;
+ }
+ cc = ptf(PTF_REQ_HORIZONTAL, &rc);
+ report(cc == 2 && rc == PTF_ERR_ALRDY_POLARIZED,
+ "KVM always provides horizontal polarization");
+ cc = ptf(PTF_REQ_VERTICAL, &rc);
+ report(cc == 2 && rc == PTF_ERR_NO_REASON,
+ "KVM doesn't support vertical polarization.");
+end:
+ report_prefix_pop();
+}
+
+static struct {
+ const char *name;
+ void (*func)(void);
+} tests[] = {
+ { "PTF", test_ptf},
+ { NULL, NULL }
+};
+
+int main(int argc, char *argv[])
+{
+ int i;
+
+ report_prefix_push("CPU Topology");
+
+ if (!test_facility(11)) {
+ report_skip("Topology facility not present");
+ goto end;
+ }
+
+ report_info("Machine level %ld", stsi_get_fc());
+
+ for (i = 0; tests[i].name; i++) {
+ report_prefix_push(tests[i].name);
+ tests[i].func();
+ report_prefix_pop();
+ }
+
+end:
+ report_prefix_pop();
+ return report_summary();
+}
diff --git a/s390x/unittests.cfg b/s390x/unittests.cfg
index 3caf81ed..3530cc4c 100644
--- a/s390x/unittests.cfg
+++ b/s390x/unittests.cfg
@@ -208,3 +208,6 @@ groups = migration
[exittime]
file = exittime.elf
smp = 2
+
+[topology]
+file = topology.elf
--
2.31.1
next prev parent reply other threads:[~2022-10-24 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 14:20 [kvm-unit-tests PATCH v5 0/2] S390x: CPU Topology Information Pierre Morel
2022-10-24 14:20 ` Pierre Morel [this message]
2022-10-24 14:20 ` [kvm-unit-tests PATCH v5 2/2] s390x: topology: Checking Configuration " Pierre Morel
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=20221024142035.22668-2-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@linux.ibm.com \
--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