Skip to contentSkip to conversation

KVM: s390: selftests: Add regression tests for CPU subfunctions

PATCH Superseded Hariharan Mari 2 participants 7 messages Aug 19, 2024

Subsystems (2)

v1 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

cover KVM: s390: selftests: Add regression tests for CPU subfunctions

This patch series introduces a set of regression tests for various s390x CPU subfunctions in KVM. The tests ensure that the KVM implementation accurately reflects the behavior of actual CPU instructions for these subfunctions.

The series adds tests for a total of 15 instructions across five patches, covering a range of operations including sorting, compression, and various cryptographic functions. Each patch follows a consistent testing pattern:

1. Obtain the KVM_S390_VM_CPU_MACHINE_SUBFUNC attribute for the VM.
2. Execute the relevant asm instructions.
3. Compare KVM-reported results with direct instruction execution results.

Testing has been performed on s390x hardware with KVM support. All tests pass successfully, verifying the correct implementation of these subfunctions in KVM.

Hariharan Mari (5):
KVM: s390: selftests: Add regression tests for SORTL and DFLTCC CPU
subfunctions
KVM: s390: selftests: Add regression tests for PRNO, KDSA and KMA
crypto subfunctions
KVM: s390: selftests: Add regression tests for KMCTR, KMF, KMO and PCC
crypto subfunctions
KVM: s390: selftests: Add regression tests for KMAC, KMC, KM, KIMD and
KLMD crypto subfunctions
KVM: s390: selftests: Add regression tests for PLO subfunctions

 tools/testing/selftests/kvm/Makefile          |   1 +
 .../selftests/kvm/include/s390x/facility.h    |  50 +++
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 343 ++++++++++++++++++
 3 files changed, 394 insertions(+)
 create mode 100644 tools/testing/selftests/kvm/include/s390x/facility.h
 create mode 100644 tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c
Signature · 1 line
2.45.2
#1 lore raw

PATCH 1/5 KVM: s390: selftests: Add regression tests for SORTL and DFLTCC CPU subfunctions

Introduce new regression tests to verify the ASM inline block in the SORTL and DFLTCC CPU subfunctions for the s390x architecture. These tests ensure that future changes to the ASM code are properly validated.

The test procedure:

1. Create a VM and request the KVM_S390_VM_CPU_MACHINE_SUBFUNC attribute from the KVM_S390_VM_CPU_MODEL group for this VM. This SUBFUNC attribute contains the results of all CPU subfunction instructions.
2. For each tested subfunction (SORTL and DFLTCC), execute the corresponding ASM instruction and capture the result array.
3. Perform a memory comparison between the results stored in the SUBFUNC attribute (obtained in step 1) and the ASM instruction results (obtained in step 2) for each tested subfunction.

This process ensures that the KVM implementation accurately reflects the behavior of the actual CPU instructions for the tested subfunctions.

---
 tools/testing/selftests/kvm/Makefile          |   1 +
 .../selftests/kvm/include/s390x/facility.h    |  50 ++++++++
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 115 ++++++++++++++++++
 3 files changed, 166 insertions(+)
 create mode 100644 tools/testing/selftests/kvm/include/s390x/facility.h
 create mode 100644 tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c
tools/testing/selftests/kvm/Makefile +1 -0
index ac280dcba996..9f418c594b55 100644
@@ -183,6 +183,7 @@ TEST_GEN_PROGS_s390x += s390x/sync_regs_test
 TEST_GEN_PROGS_s390x += s390x/tprot
 TEST_GEN_PROGS_s390x += s390x/cmma_test
 TEST_GEN_PROGS_s390x += s390x/debug_test
+TEST_GEN_PROGS_s390x += s390x/cpumodel_subfuncs_test
 TEST_GEN_PROGS_s390x += s390x/shared_zeropage_test
 TEST_GEN_PROGS_s390x += demand_paging_test
 TEST_GEN_PROGS_s390x += dirty_log_test
tools/testing/selftests/kvm/include/s390x/facility.h new file +50 -0

50 lines not on this page · raw message

tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c new file +115 -0

115 lines not on this page · raw message

Signature · 1 line
2.45.2
#2 lore raw

PATCH 2/5 KVM: s390: selftests: Add regression tests for PRNO, KDSA and KMA crypto subfunctions

In reply to Hariharan Mari

Extend the existing regression test framework for s390x CPU subfunctions to include tests for the PRNO (Perform Random Number Operation), KDSA (Compute Digital Signature Authentication) and KMA (Cipher Message with Authentication) crypto functions.

The test procedure follows the established pattern:

1. Obtain KVM_S390_VM_CPU_MACHINE_SUBFUNC attribute for the VM.
2. Execute PRNO, KDSA and KMA instructions.
3. Compare KVM-reported results with direct instruction execution results.

---
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 51 +++++++++++++++++++
 1 file changed, 51 insertions(+)
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +51 -0
index 45add61cba91..c2ae5b270f50 100644
@@ -37,6 +37,48 @@ static void get_cpu_machine_subfuntions(struct kvm_vm *vm,
 	TEST_ASSERT(!r, "Get cpu subfunctions failed r=%d errno=%d", r, errno);
 }
 
+/*
+ * Testing Crypto Perform Random Number Operation (PRNO) CPU subfunction's
+ * ASM block
+ */
+static void test_prno_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb93c0000,2,4\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Cipher Message with Authentication (KMA) CPU subfunction's
+ * ASM block
+ */
+static void test_kma_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rrf,0xb9290000,2,4,6,0\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Compute Digital Signature Authentication (KDSA) CPU
+ * subfunction's ASM block
+ */
+static void test_kdsa_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb93a0000,0,2\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
 /*
  * Testing Sort Lists (SORTL) CPU subfunction's ASM block
  */
@@ -72,6 +114,15 @@ struct testdef {
 	testfunc_t test;
 	bool facility_bit;
 } testlist[] = {
+	/* MSA5 - Facility bit 57 */
+	{ "PPNO", cpu_subfunc.ppno, sizeof(cpu_subfunc.ppno),
+		test_prno_asm_block, 57 },
+	/* MSA8 - Facility bit 146 */
+	{ "KMA", cpu_subfunc.kma, sizeof(cpu_subfunc.kma),
+		test_kma_asm_block, 146 },
+	/* MSA9 - Facility bit 155 */
+	{ "KDSA", cpu_subfunc.kdsa, sizeof(cpu_subfunc.kdsa),
+		test_kdsa_asm_block, 155 },
 	/* SORTL - Facility bit 150 */
 	{ "SORTL", cpu_subfunc.sortl, sizeof(cpu_subfunc.sortl),
 		test_sortl_asm_block, 150 },
Signature · 1 line
2.45.2
#3 lore raw

PATCH 3/5 KVM: s390: selftests: Add regression tests for KMCTR, KMF, KMO and PCC crypto subfunctions

In reply to Hariharan Mari

Extend the existing regression test framework for s390x CPU subfunctions to include tests for the KMCTR (Cipher Message with Counter) KMO (Cipher Message with Output Feedback), KMF (Cipher Message with Cipher Feedback) and PCC (Perform Cryptographic Computation) crypto functions.

The test procedure follows the established pattern.

---
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 65 +++++++++++++++++++
 1 file changed, 65 insertions(+)
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +65 -0
index c2ae5b270f50..6ef9e855ac65 100644
@@ -37,6 +37,62 @@ static void get_cpu_machine_subfuntions(struct kvm_vm *vm,
 	TEST_ASSERT(!r, "Get cpu subfunctions failed r=%d errno=%d", r, errno);
 }
 
+/*
+ * Testing Crypto Cipher Message with Counter (KMCTR) CPU subfunction's ASM
+ * block
+ */
+static void test_kmctr_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rrf,0xb92d0000,2,4,6,0\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Cipher Message with Cipher Feedback (KMF) CPU subfunction's
+ * ASM block
+ */
+static void test_kmf_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb92a0000,2,4\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Cipher Message with Output Feedback (KMO) CPU subfunction's
+ * ASM block
+ */
+static void test_kmo_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb92b0000,2,4\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Perform Cryptographic Computation (PCC) CPU subfunction's
+ * ASM block
+ */
+static void test_pcc_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb92c0000,0,0\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
 /*
  * Testing Crypto Perform Random Number Operation (PRNO) CPU subfunction's
  * ASM block
@@ -114,6 +170,15 @@ struct testdef {
 	testfunc_t test;
 	bool facility_bit;
 } testlist[] = {
+	/* MSA - Facility bit 77 */
+	{ "KMCTR", cpu_subfunc.kmctr, sizeof(cpu_subfunc.kmctr),
+		test_kmctr_asm_block, 77 },
+	{ "KMF", cpu_subfunc.kmf, sizeof(cpu_subfunc.kmf),
+		test_kmf_asm_block, 77 },
+	{ "KMO", cpu_subfunc.kmo, sizeof(cpu_subfunc.kmo),
+		test_kmo_asm_block, 77 },
+	{ "PCC", cpu_subfunc.pcc, sizeof(cpu_subfunc.pcc),
+		test_pcc_asm_block, 77 },
 	/* MSA5 - Facility bit 57 */
 	{ "PPNO", cpu_subfunc.ppno, sizeof(cpu_subfunc.ppno),
 		test_prno_asm_block, 57 },
Signature · 1 line
2.45.2
#4 lore raw

PATCH 4/5 KVM: s390: selftests: Add regression tests for KMAC, KMC, KM, KIMD and KLMD crypto subfunctions

In reply to Hariharan Mari

Extend the existing regression test framework for s390x CPU subfunctions to include tests for the KMAC (Compute Message Authentication Code), KMC (Cipher Message with Chaining), KM (Cipher Message) KIMD (Compute Intermediate Message Digest) and KLMD (Compute Last Message Digest) crypto functions.

The test procedure follows the established pattern.

---
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 78 +++++++++++++++++++
 1 file changed, 78 insertions(+)
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +78 -0
index 6ef9e855ac65..901c99fe79d9 100644
@@ -37,6 +37,73 @@ static void get_cpu_machine_subfuntions(struct kvm_vm *vm,
 	TEST_ASSERT(!r, "Get cpu subfunctions failed r=%d errno=%d", r, errno);
 }
 
+/*
+ * Testing Crypto Compute Message Authentication Code (KMAC) CPU subfunction's
+ * ASM block
+ */
+static void test_kmac_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb91e0000,0,2\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Cipher Message with Chaining (KMC) CPU subfunction's ASM block
+ */
+static void test_kmc_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb92f0000,2,4\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Cipher Message (KM) CPU subfunction's ASM block
+ */
+static void test_km_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb92e0000,2,4\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Compute Intermediate Message Digest (KIMD) CPU subfunction's
+ * ASM block
+ */
+static void test_kimd_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb93e0000,0,2\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
+/*
+ * Testing Crypto Compute Last Message Digest (KLMD) CPU subfunction's ASM block
+ */
+static void test_klmd_asm_block(u8 (*query)[16])
+{
+	asm volatile("	la	%%r1,%[query]\n"
+			"	xgr	%%r0,%%r0\n"
+			"	.insn	rre,0xb93f0000,0,2\n"
+			: [query] "=R" (*query)
+			:
+			: "cc", "r0", "r1");
+}
+
 /*
  * Testing Crypto Cipher Message with Counter (KMCTR) CPU subfunction's ASM
  * block
@@ -170,6 +237,17 @@ struct testdef {
 	testfunc_t test;
 	bool facility_bit;
 } testlist[] = {
+	/* MSA - Facility bit 17 */
+	{ "KMAC", cpu_subfunc.kmac, sizeof(cpu_subfunc.kmac),
+		test_kmac_asm_block, 17 },
+	{ "KMC", cpu_subfunc.kmc, sizeof(cpu_subfunc.kmc),
+		test_kmc_asm_block, 17 },
+	{ "KM", cpu_subfunc.km, sizeof(cpu_subfunc.km),
+		test_km_asm_block, 17 },
+	{ "KIMD", cpu_subfunc.kimd, sizeof(cpu_subfunc.kimd),
+		test_kimd_asm_block, 17 },
+	{ "KLMD", cpu_subfunc.klmd, sizeof(cpu_subfunc.klmd),
+		test_klmd_asm_block, 17 },
 	/* MSA - Facility bit 77 */
 	{ "KMCTR", cpu_subfunc.kmctr, sizeof(cpu_subfunc.kmctr),
 		test_kmctr_asm_block, 77 },
Signature · 1 line
2.45.2
#5 lore raw

PATCH 5/5 KVM: s390: selftests: Add regression tests for PLO subfunctions

In reply to Hariharan Mari

Extend the existing regression test framework for s390x CPU subfunctions to include tests for the Perform Locked Operation (PLO) subfunction functions.

PLO was introduced in the very first 64-bit machine generation. Hence it is assumed PLO is always installed in the Z Arch. The test procedure follows the established pattern.

---
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 36 ++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +35 -1
index 901c99fe79d9..255984a52365 100644
@@ -20,6 +20,8 @@
 
 #include "kvm_util.h"
 
+#define U8_MAX  ((u8)~0U)
+
 /**
  * Query available CPU subfunctions
  */
@@ -37,6 +39,33 @@ static void get_cpu_machine_subfuntions(struct kvm_vm *vm,
 	TEST_ASSERT(!r, "Get cpu subfunctions failed r=%d errno=%d", r, errno);
 }
 
+static inline int plo_test_bit(unsigned char nr)
+{
+	unsigned long function = (unsigned long)nr | 0x100;
+	int cc;
+
+	asm volatile("	lgr	0,%[function]\n"
+			/* Parameter registers are ignored for "test bit" */
+			"	plo	0,0,0,0(0)\n"
+			"	ipm	%0\n"
+			"	srl	%0,28\n"
+			: "=d" (cc)
+			: [function] "d" (function)
+			: "cc", "0");
+	return cc == 0;
+}
+
+/*
+ * Testing Perform Locked Operation (PLO) CPU subfunction's ASM block
+ */
+static void test_plo_asm_block(u8 (*query)[32])
+{
+	for (int i = 0; i <= U8_MAX; ++i) {
+		if (plo_test_bit(i))
+			(*query)[i >> 3] |= 0x80 >> (i & 7);
+	}
+}
+
 /*
  * Testing Crypto Compute Message Authentication Code (KMAC) CPU subfunction's
  * ASM block
@@ -235,8 +264,13 @@ struct testdef {
 	u8 *subfunc_array;
 	size_t array_size;
 	testfunc_t test;
-	bool facility_bit;
+	int facility_bit;
 } testlist[] = {
+	/*  PLO was introduced in the very first 64-bit machine generation.
+	 *  Hence it is assumed PLO is always installed in Z Arch .
+	 */
+	{ "PLO", cpu_subfunc.plo, sizeof(cpu_subfunc.plo),
+		test_plo_asm_block, 1 },
 	/* MSA - Facility bit 17 */
 	{ "KMAC", cpu_subfunc.kmac, sizeof(cpu_subfunc.kmac),
 		test_kmac_asm_block, 17 },
Signature · 1 line
2.45.2
#6 lore raw

Re: [PATCH v1 5/5] KVM: s390: selftests: Add regression tests for PLO subfunctions

Quoted 63 lines · Hariharan Mari

Extend the existing regression test framework for s390x CPU subfunctions to include tests for the Perform Locked Operation (PLO) subfunction functions.

PLO was introduced in the very first 64-bit machine generation. Hence it is assumed PLO is always installed in the Z Arch. The test procedure follows the established pattern.

---
 .../kvm/s390x/cpumodel_subfuncs_test.c        | 36 ++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +29 -0
index 901c99fe79d9..255984a52365 100644
@@ -20,6 +20,8 @@
 
 #include "kvm_util.h"
 
+#define U8_MAX  ((u8)~0U)
+
 /**
  * Query available CPU subfunctions
  */
@@ -37,6 +39,33 @@ static void get_cpu_machine_subfuntions(struct kvm_vm *vm,
 	TEST_ASSERT(!r, "Get cpu subfunctions failed r=%d errno=%d", r, errno);
 }
 
+static inline int plo_test_bit(unsigned char nr)
+{
+	unsigned long function = (unsigned long)nr | 0x100;
+	int cc;
+
+	asm volatile("	lgr	0,%[function]\n"
+			/* Parameter registers are ignored for "test bit" */
+			"	plo	0,0,0,0(0)\n"
+			"	ipm	%0\n"
+			"	srl	%0,28\n"
+			: "=d" (cc)
+			: [function] "d" (function)
+			: "cc", "0");
+	return cc == 0;
+}
+
+/*
+ * Testing Perform Locked Operation (PLO) CPU subfunction's ASM block
+ */
+static void test_plo_asm_block(u8 (*query)[32])
+{
+	for (int i = 0; i <= U8_MAX; ++i) {
+		if (plo_test_bit(i))
+			(*query)[i >> 3] |= 0x80 >> (i & 7);
+	}
+}
+
 /*
  * Testing Crypto Compute Message Authentication Code (KMAC) CPU subfunction's
  * ASM block

tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c struct testdef { · line 267

Quoted 5 lines
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +1 -1
@@ -235,8 +264,13 @@ struct testdef {
 	u8 *subfunc_array;
 	size_t array_size;
 	testfunc_t test;
-	bool facility_bit;
+	int facility_bit;

Why change that to int here?

Quoted 9 lines
tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c +5 -0
 } testlist[] = {
+	/*  PLO was introduced in the very first 64-bit machine generation.
+	 *  Hence it is assumed PLO is always installed in Z Arch .
+	 */
+	{ "PLO", cpu_subfunc.plo, sizeof(cpu_subfunc.plo),
+		test_plo_asm_block, 1 },
 	/* MSA - Facility bit 17 */
 	{ "KMAC", cpu_subfunc.kmac, sizeof(cpu_subfunc.kmac),
 		test_kmac_asm_block, 17 },