[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <821e840f-c167-611a-e954-38173a90c0a5@linux.ibm.com>
Date: Tue, 8 Mar 2022 11:16:23 +0100
From: Christian Borntraeger <borntraeger@...ux.ibm.com>
To: Janis Schoetterl-Glausch <scgl@...ux.ibm.com>,
Janosch Frank <frankja@...ux.ibm.com>,
Claudio Imbrenda <imbrenda@...ux.ibm.com>,
Shuah Khan <shuah@...nel.org>
Cc: Thomas Huth <thuth@...hat.com>,
David Hildenbrand <david@...hat.com>, kvm@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] memop selftest for storage key checking
Can you send this as a separate thread (not inside the original thread). Otherwise things like b4 get confused and people might also overlook this.
Am 25.02.22 um 16:53 schrieb Janis Schoetterl-Glausch:
> Refactor memop selftest and add tests.
> Add storage key tests, both for success as well as failure cases.
> Similarly test both vcpu and vm ioctls.
>
> v1 -> v2
> * restructure commits
> * get rid of test_* wrapper functions that hid vm.vm
> * minor changes
>
> v0 -> v2
> * complete rewrite
>
> v1: https://lore.kernel.org/kvm/20220217145336.1794778-1-scgl@linux.ibm.com/
> v0: https://lore.kernel.org/kvm/20220211182215.2730017-11-scgl@linux.ibm.com/
>
> Janis Schoetterl-Glausch (5):
> KVM: s390: selftests: Split memop tests
> KVM: s390: selftests: Add macro as abstraction for MEM_OP
> KVM: s390: selftests: Add named stages for memop test
> KVM: s390: selftests: Add more copy memop tests
> KVM: s390: selftests: Add error memop tests
>
> tools/testing/selftests/kvm/s390x/memop.c | 734 ++++++++++++++++++----
> 1 file changed, 616 insertions(+), 118 deletions(-)
>
>
> base-commit: ee6a569d3bf64c9676eee3eecb861fb01cc11311
Powered by blists - more mailing lists