public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
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 2/4] KVM: s390: selftests: Use TAP interface in the sync_regs test
Date: Wed, 20 Apr 2022 11:29:13 +0200	[thread overview]
Message-ID: <0f208aa9-9e0b-cabc-575e-ac384910ac52@linux.ibm.com> (raw)
In-Reply-To: <20220419185857.128351-3-thuth@redhat.com>

On 4/19/22 20:58, Thomas Huth wrote:
> The sync_regs 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.
> To be able to distinguish the different sub-tests more easily, we
> also break up the huge main() function here in more fine grained
> parts.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>

Acked-by: Janosch Frank <frankja@linux.ibm.com>

> ---
>   .../selftests/kvm/s390x/sync_regs_test.c      | 87 ++++++++++++++-----
>   1 file changed, 66 insertions(+), 21 deletions(-)
> 
> diff --git a/tools/testing/selftests/kvm/s390x/sync_regs_test.c b/tools/testing/selftests/kvm/s390x/sync_regs_test.c
> index caf7b8859a94..c3719c92f4e8 100644
> --- a/tools/testing/selftests/kvm/s390x/sync_regs_test.c
> +++ b/tools/testing/selftests/kvm/s390x/sync_regs_test.c
> @@ -21,6 +21,7 @@
>   #include "test_util.h"
>   #include "kvm_util.h"
>   #include "diag318_test_handler.h"
> +#include "kselftest.h"
>   
>   #define VCPU_ID 5
>   
> @@ -74,27 +75,9 @@ static void compare_sregs(struct kvm_sregs *left, struct kvm_sync_regs *right)
>   #define TEST_SYNC_FIELDS   (KVM_SYNC_GPRS|KVM_SYNC_ACRS|KVM_SYNC_CRS|KVM_SYNC_DIAG318)
>   #define INVALID_SYNC_FIELD 0x80000000
>   
> -int main(int argc, char *argv[])
> +void test_read_invalid(struct kvm_vm *vm, struct kvm_run *run)
>   {
> -	struct kvm_vm *vm;
> -	struct kvm_run *run;
> -	struct kvm_regs regs;
> -	struct kvm_sregs sregs;
> -	int rv, cap;
> -
> -	/* Tell stdout not to buffer its content */
> -	setbuf(stdout, NULL);
> -
> -	cap = kvm_check_cap(KVM_CAP_SYNC_REGS);
> -	if (!cap) {
> -		print_skip("CAP_SYNC_REGS not supported");
> -		exit(KSFT_SKIP);
> -	}
> -
> -	/* Create VM */
> -	vm = vm_create_default(VCPU_ID, 0, guest_code);
> -
> -	run = vcpu_state(vm, VCPU_ID);
> +	int rv;
>   
>   	/* Request reading invalid register set from VCPU. */
>   	run->kvm_valid_regs = INVALID_SYNC_FIELD;
> @@ -110,6 +93,11 @@ int main(int argc, char *argv[])
>   		    "Invalid kvm_valid_regs did not cause expected KVM_RUN error: %d\n",
>   		    rv);
>   	vcpu_state(vm, VCPU_ID)->kvm_valid_regs = 0;
> +}
> +
> +void test_set_invalid(struct kvm_vm *vm, struct kvm_run *run)
> +{
> +	int rv;
>   
>   	/* Request setting invalid register set into VCPU. */
>   	run->kvm_dirty_regs = INVALID_SYNC_FIELD;
> @@ -125,6 +113,13 @@ int main(int argc, char *argv[])
>   		    "Invalid kvm_dirty_regs did not cause expected KVM_RUN error: %d\n",
>   		    rv);
>   	vcpu_state(vm, VCPU_ID)->kvm_dirty_regs = 0;
> +}
> +
> +void test_req_and_verify_all_valid_regs(struct kvm_vm *vm, struct kvm_run *run)
> +{
> +	struct kvm_sregs sregs;
> +	struct kvm_regs regs;
> +	int rv;
>   
>   	/* Request and verify all valid register sets. */
>   	run->kvm_valid_regs = TEST_SYNC_FIELDS;
> @@ -146,6 +141,13 @@ int main(int argc, char *argv[])
>   
>   	vcpu_sregs_get(vm, VCPU_ID, &sregs);
>   	compare_sregs(&sregs, &run->s.regs);
> +}
> +
> +void test_set_and_verify_various_reg_values(struct kvm_vm *vm, struct kvm_run *run)
> +{
> +	struct kvm_sregs sregs;
> +	struct kvm_regs regs;
> +	int rv;
>   
>   	/* Set and verify various register values */
>   	run->s.regs.gprs[11] = 0xBAD1DEA;
> @@ -180,6 +182,11 @@ int main(int argc, char *argv[])
>   
>   	vcpu_sregs_get(vm, VCPU_ID, &sregs);
>   	compare_sregs(&sregs, &run->s.regs);
> +}
> +
> +void test_clear_kvm_dirty_regs_bits(struct kvm_vm *vm, struct kvm_run *run)
> +{
> +	int rv;
>   
>   	/* Clear kvm_dirty_regs bits, verify new s.regs values are
>   	 * overwritten with existing guest values.
> @@ -200,8 +207,46 @@ int main(int argc, char *argv[])
>   	TEST_ASSERT(run->s.regs.diag318 != 0x4B1D,
>   		    "diag318 sync regs value incorrect 0x%llx.",
>   		    run->s.regs.diag318);
> +}
> +
> +struct testdef {
> +	const char *name;
> +	void (*test)(struct kvm_vm *vm, struct kvm_run *run);
> +} testlist[] = {
> +	{ "read invalid", test_read_invalid },
> +	{ "set invalid", test_set_invalid },
> +	{ "request+verify all valid regs", test_req_and_verify_all_valid_regs },
> +	{ "set+verify various regs", test_set_and_verify_various_reg_values },
> +	{ "clear kvm_dirty_regs bits", test_clear_kvm_dirty_regs_bits },
> +};
> +
> +int main(int argc, char *argv[])
> +{
> +	static struct kvm_run *run;
> +	static struct kvm_vm *vm;
> +	int idx;
> +
> +	/* Tell stdout not to buffer its content */
> +	setbuf(stdout, NULL);
> +
> +	ksft_print_header();
> +
> +	if (!kvm_check_cap(KVM_CAP_SYNC_REGS))
> +		ksft_exit_skip("CAP_SYNC_REGS not supported");
> +
> +	ksft_set_plan(ARRAY_SIZE(testlist));
> +
> +	/* Create VM */
> +	vm = vm_create_default(VCPU_ID, 0, guest_code);
> +
> +	run = vcpu_state(vm, VCPU_ID);
> +
> +	for (idx = 0; idx < ARRAY_SIZE(testlist); idx++) {
> +		testlist[idx].test(vm, run);
> +		ksft_test_result_pass("%s\n", testlist[idx].name);
> +	}
>   
>   	kvm_vm_free(vm);
>   
> -	return 0;
> +	ksft_finished();
>   }


  reply	other threads:[~2022-04-20  9:29 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 [this message]
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
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=0f208aa9-9e0b-cabc-575e-ac384910ac52@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox