From: Thomas Huth <thuth@redhat.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-s390@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH v3 5/9] KVM: s390: selftest: memop: Move testlist into main
Date: Tue, 22 Nov 2022 08:52:38 +0100 [thread overview]
Message-ID: <c801611e-61db-73d2-2ff1-cd06350215b2@redhat.com> (raw)
In-Reply-To: <20221117221758.66326-6-scgl@linux.ibm.com>
On 17/11/2022 23.17, Janis Schoetterl-Glausch wrote:
> This allows checking if the necessary requirements for a test case are
> met via an arbitrary expression. In particular, it is easy to check if
> certain bits are set in the memop extension capability.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> ---
> tools/testing/selftests/kvm/s390x/memop.c | 132 +++++++++++-----------
> 1 file changed, 66 insertions(+), 66 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/s390x/memop.c b/tools/testing/selftests/kvm/s390x/memop.c
> index 286185a59238..10f34c629cac 100644
> --- a/tools/testing/selftests/kvm/s390x/memop.c
> +++ b/tools/testing/selftests/kvm/s390x/memop.c
> @@ -690,87 +690,87 @@ static void test_errors(void)
> kvm_vm_free(t.kvm_vm);
> }
>
> -struct testdef {
> - const char *name;
> - void (*test)(void);
> - int extension;
> -} testlist[] = {
> - {
> - .name = "simple copy",
> - .test = test_copy,
> - },
> - {
> - .name = "generic error checks",
> - .test = test_errors,
> - },
> - {
> - .name = "copy with storage keys",
> - .test = test_copy_key,
> - .extension = 1,
> - },
> - {
> - .name = "copy with key storage protection override",
> - .test = test_copy_key_storage_prot_override,
> - .extension = 1,
> - },
> - {
> - .name = "copy with key fetch protection",
> - .test = test_copy_key_fetch_prot,
> - .extension = 1,
> - },
> - {
> - .name = "copy with key fetch protection override",
> - .test = test_copy_key_fetch_prot_override,
> - .extension = 1,
> - },
> - {
> - .name = "error checks with key",
> - .test = test_errors_key,
> - .extension = 1,
> - },
> - {
> - .name = "termination",
> - .test = test_termination,
> - .extension = 1,
> - },
> - {
> - .name = "error checks with key storage protection override",
> - .test = test_errors_key_storage_prot_override,
> - .extension = 1,
> - },
> - {
> - .name = "error checks without key fetch prot override",
> - .test = test_errors_key_fetch_prot_override_not_enabled,
> - .extension = 1,
> - },
> - {
> - .name = "error checks with key fetch prot override",
> - .test = test_errors_key_fetch_prot_override_enabled,
> - .extension = 1,
> - },
> -};
>
> int main(int argc, char *argv[])
> {
> int extension_cap, idx;
>
> + setbuf(stdout, NULL); /* Tell stdout not to buffer its content */
> TEST_REQUIRE(kvm_has_cap(KVM_CAP_S390_MEM_OP));
> + extension_cap = kvm_check_cap(KVM_CAP_S390_MEM_OP_EXTENSION);
>
> - setbuf(stdout, NULL); /* Tell stdout not to buffer its content */
> + struct testdef {
> + const char *name;
> + void (*test)(void);
> + bool requirements_met;
> + } testlist[] = {
> + {
> + .name = "simple copy",
> + .test = test_copy,
> + .requirements_met = true,
> + },
> + {
> + .name = "generic error checks",
> + .test = test_errors,
> + .requirements_met = true,
> + },
> + {
> + .name = "copy with storage keys",
> + .test = test_copy_key,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "copy with key storage protection override",
> + .test = test_copy_key_storage_prot_override,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "copy with key fetch protection",
> + .test = test_copy_key_fetch_prot,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "copy with key fetch protection override",
> + .test = test_copy_key_fetch_prot_override,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "error checks with key",
> + .test = test_errors_key,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "termination",
> + .test = test_termination,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "error checks with key storage protection override",
> + .test = test_errors_key_storage_prot_override,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "error checks without key fetch prot override",
> + .test = test_errors_key_fetch_prot_override_not_enabled,
> + .requirements_met = extension_cap > 0,
> + },
> + {
> + .name = "error checks with key fetch prot override",
> + .test = test_errors_key_fetch_prot_override_enabled,
> + .requirements_met = extension_cap > 0,
I wonder whether it would rather make sense to check for "extension_cap & 1"
instead of "extension_cap > 0" ?
Anyway:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2022-11-22 7:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 22:17 [PATCH v3 0/9] KVM: s390: Extend MEM_OP ioctl by storage key checked cmpxchg Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 1/9] " Janis Schoetterl-Glausch
2022-11-18 10:12 ` Heiko Carstens
2022-11-18 14:37 ` Thomas Huth
2022-11-18 15:15 ` Heiko Carstens
2022-11-21 17:41 ` Janis Schoetterl-Glausch
2022-12-01 16:15 ` Claudio Imbrenda
2022-12-01 17:44 ` Janis Schoetterl-Glausch
2022-12-02 9:00 ` Claudio Imbrenda
2022-11-17 22:17 ` [PATCH v3 2/9] Documentation: KVM: s390: Describe KVM_S390_MEMOP_F_CMPXCHG Janis Schoetterl-Glausch
2022-11-18 1:50 ` Bagas Sanjaya
2022-11-21 17:44 ` Janis Schoetterl-Glausch
2022-11-22 7:47 ` Thomas Huth
2022-11-22 13:10 ` Janis Schoetterl-Glausch
2022-11-25 8:52 ` Nico Boehr
2022-12-01 16:21 ` Claudio Imbrenda
2022-11-17 22:17 ` [PATCH v3 3/9] KVM: s390: selftest: memop: Pass mop_desc via pointer Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 4/9] KVM: s390: selftest: memop: Replace macros by functions Janis Schoetterl-Glausch
2022-12-01 16:28 ` Claudio Imbrenda
2022-12-01 17:58 ` Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 5/9] KVM: s390: selftest: memop: Move testlist into main Janis Schoetterl-Glausch
2022-11-22 7:52 ` Thomas Huth [this message]
2022-11-22 9:34 ` Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 6/9] KVM: s390: selftest: memop: Add cmpxchg tests Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 7/9] KVM: s390: selftest: memop: Add bad address test Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 8/9] KVM: s390: selftest: memop: Fix typo Janis Schoetterl-Glausch
2022-11-17 22:17 ` [PATCH v3 9/9] KVM: s390: selftest: memop: Fix wrong address being used in test Janis Schoetterl-Glausch
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=c801611e-61db-73d2-2ff1-cd06350215b2@redhat.com \
--to=thuth@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=scgl@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).