From: Christoph Schlameuss <schlameuss@linux.ibm.com>
To: Hariharan Mari <hari55@linux.ibm.com>, linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
shuah@kernel.org, frankja@linux.ibm.com,
borntraeger@linux.ibm.com, imbrenda@linux.ibm.com,
david@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v1 5/5] KVM: s390: selftests: Add regression tests for PLO subfunctions
Date: Mon, 19 Aug 2024 18:04:01 +0200 [thread overview]
Message-ID: <ZsNs8aIXM71NCG4h@darkmoore> (raw)
In-Reply-To: <20240819140040.1087552-6-hari55@linux.ibm.com>
On Mon Aug 19, 2024 at 3:54 PM CEST, Hariharan Mari wrote:
> 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.
>
> Suggested-by: Janosch Frank <frankja@linux.ibm.com>
> Signed-off-by: Hariharan Mari <hari55@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> .../kvm/s390x/cpumodel_subfuncs_test.c | 36 ++++++++++++++++++-
> 1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c b/tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c
> index 901c99fe79d9..255984a52365 100644
> --- a/tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c
> +++ b/tools/testing/selftests/kvm/s390x/cpumodel_subfuncs_test.c
> @@ -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;
Why change that to int here?
> } 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 },
prev parent reply other threads:[~2024-08-19 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:54 [PATCH v1 0/5] KVM: s390: selftests: Add regression tests for CPU subfunctions Hariharan Mari
2024-08-19 13:54 ` [PATCH v1 1/5] KVM: s390: selftests: Add regression tests for SORTL and DFLTCC " Hariharan Mari
2024-08-19 13:54 ` [PATCH v1 2/5] KVM: s390: selftests: Add regression tests for PRNO, KDSA and KMA crypto subfunctions Hariharan Mari
2024-08-19 13:54 ` [PATCH v1 3/5] KVM: s390: selftests: Add regression tests for KMCTR, KMF, KMO and PCC " Hariharan Mari
2024-08-19 13:54 ` [PATCH v1 4/5] KVM: s390: selftests: Add regression tests for KMAC, KMC, KM, KIMD and KLMD " Hariharan Mari
2024-08-19 13:54 ` [PATCH v1 5/5] KVM: s390: selftests: Add regression tests for PLO subfunctions Hariharan Mari
2024-08-19 16:04 ` Christoph Schlameuss [this message]
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=ZsNs8aIXM71NCG4h@darkmoore \
--to=schlameuss@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hari55@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/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).