From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 3/4] KVM: s390: selftests: Use TAP interface in the tprot test
Date: Wed, 20 Apr 2022 12:23:00 +0200 [thread overview]
Message-ID: <65711eda-76da-882c-ee3e-a0f8805943ab@linux.ibm.com> (raw)
In-Reply-To: <20220419185857.128351-4-thuth@redhat.com>
On 4/19/22 20:58, Thomas Huth wrote:
> The tprot test currently does not have any output (unless one of
> the TEST_ASSERT statement fails), so it's hard to say for a user
> whether a certain new sub-test has been included in the binary or
> not. Let's make this a little bit more user-friendly and include
> some TAP output via the kselftests.h interface.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Some comments below.
> ---
> tools/testing/selftests/kvm/s390x/tprot.c | 28 +++++++++++++++++++----
> 1 file changed, 23 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/s390x/tprot.c b/tools/testing/selftests/kvm/s390x/tprot.c
> index c097b9db495e..baba883d7a6d 100644
> --- a/tools/testing/selftests/kvm/s390x/tprot.c
> +++ b/tools/testing/selftests/kvm/s390x/tprot.c
> @@ -8,6 +8,7 @@
> #include <sys/mman.h>
> #include "test_util.h"
> #include "kvm_util.h"
> +#include "kselftest.h"
>
> #define PAGE_SHIFT 12
> #define PAGE_SIZE (1 << PAGE_SHIFT)
> @@ -63,12 +64,12 @@ static enum permission test_protection(void *addr, uint8_t key)
> }
>
> enum stage {
> - STAGE_END,
> STAGE_INIT_SIMPLE,
> TEST_SIMPLE,
> STAGE_INIT_FETCH_PROT_OVERRIDE,
> TEST_FETCH_PROT_OVERRIDE,
> TEST_STORAGE_PROT_OVERRIDE,
> + STAGE_END /* this must be the last entry */
...so we can use it to calculate the test number
> };
>
> struct test {
> @@ -182,7 +183,7 @@ static void guest_code(void)
> GUEST_SYNC(perform_next_stage(&i, mapped_0));
> }
>
> @@ -212,9 +222,13 @@ int main(int argc, char *argv[])
> HOST_SYNC(vm, TEST_SIMPLE);
>
> guest_0_page = vm_vaddr_alloc(vm, PAGE_SIZE, 0);
> - if (guest_0_page != 0)
> - print_skip("Did not allocate page at 0 for fetch protection override tests");
> - HOST_SYNC(vm, STAGE_INIT_FETCH_PROT_OVERRIDE);
> + if (guest_0_page != 0) {
Maybe add:
/* Use no_tap so we don't get a PASS print */
> + HOST_SYNC_NO_TAP(vm, STAGE_INIT_FETCH_PROT_OVERRIDE);
> + ksft_test_result_skip("STAGE_INIT_FETCH_PROT_OVERRIDE - "
> + "Did not allocate page at 0\n");
> + } else {
> + HOST_SYNC(vm, STAGE_INIT_FETCH_PROT_OVERRIDE);
> + }
Otherwise this would look weird.
> if (guest_0_page == 0)
> mprotect(addr_gva2hva(vm, (vm_vaddr_t)0), PAGE_SIZE, PROT_READ);
> run->s.regs.crs[0] |= CR0_FETCH_PROTECTION_OVERRIDE;
> @@ -224,4 +238,8 @@ int main(int argc, char *argv[])
> run->s.regs.crs[0] |= CR0_STORAGE_PROTECTION_OVERRIDE;
> run->kvm_dirty_regs = KVM_SYNC_CRS;
> HOST_SYNC(vm, TEST_STORAGE_PROT_OVERRIDE);
> +
> + kvm_vm_free(vm);
> +
> + ksft_finished();
> }
next prev parent reply other threads:[~2022-04-20 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 18:58 [PATCH v2 0/4] KVM: s390: selftests: Provide TAP output in tests Thomas Huth
2022-04-19 18:58 ` [PATCH v2 1/4] KVM: s390: selftests: Use TAP interface in the memop test Thomas Huth
2022-04-20 9:21 ` Janosch Frank
2022-04-19 18:58 ` [PATCH v2 2/4] KVM: s390: selftests: Use TAP interface in the sync_regs test Thomas Huth
2022-04-20 9:29 ` Janosch Frank
2022-04-19 18:58 ` [PATCH v2 3/4] KVM: s390: selftests: Use TAP interface in the tprot test Thomas Huth
2022-04-20 10:23 ` Janosch Frank [this message]
2022-04-20 11:38 ` Janis Schoetterl-Glausch
2022-04-20 11:46 ` Thomas Huth
2022-04-20 12:06 ` Janis Schoetterl-Glausch
2022-04-19 18:58 ` [PATCH v2 4/4] KVM: s390: selftests: Use TAP interface in the reset test Thomas Huth
2022-04-20 10:34 ` Janosch Frank
2022-04-29 6:21 ` Thomas Huth
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=65711eda-76da-882c-ee3e-a0f8805943ab@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@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=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.