From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
kvm@vger.kernel.org, Janosch Frank <frankja@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 v3 0/4] KVM: s390: selftests: Provide TAP output in tests
Date: Tue, 31 May 2022 11:06:48 +0200 [thread overview]
Message-ID: <9b3c88f2-ca23-df23-4a5b-d86b0b38a6aa@linux.ibm.com> (raw)
In-Reply-To: <e39149e0-e6c4-f850-cd0f-cbdb453ee0c2@redhat.com>
Am 31.05.22 um 10:02 schrieb Thomas Huth:
> On 29/04/2022 08.37, Thomas Huth wrote:
>> This patch series is motivated by Shuah's suggestion here:
>>
>> https://lore.kernel.org/kvm/d576d8f7-980f-3bc6-87ad-5a6ae45609b8@linuxfoundation.org/
>>
>> Many s390x KVM selftests do not output any information about which
>> tests have been run, so it's hard to say whether a test binary
>> contains a certain sub-test or not. To improve this situation let's
>> add some TAP output via the kselftest.h interface to these tests,
>> so that it easier to understand what has been executed or not.
>>
>> v3:
>> - Added comments / fixed cosmetics according to Janosch's and
>> Janis' reviews of the v2 series
>> - Added Reviewed-by tags from the v2 series
>>
>> v2:
>> - Reworked the extension checking in the first patch
>> - Make sure to always print the TAP 13 header in the second patch
>> - Reworked the SKIP printing in the third patch
>>
>> Thomas Huth (4):
>> KVM: s390: selftests: Use TAP interface in the memop test
>> KVM: s390: selftests: Use TAP interface in the sync_regs test
>> KVM: s390: selftests: Use TAP interface in the tprot test
>> KVM: s390: selftests: Use TAP interface in the reset test
>>
>> tools/testing/selftests/kvm/s390x/memop.c | 90 +++++++++++++++----
>> tools/testing/selftests/kvm/s390x/resets.c | 38 ++++++--
>> .../selftests/kvm/s390x/sync_regs_test.c | 87 +++++++++++++-----
>> tools/testing/selftests/kvm/s390x/tprot.c | 29 ++++--
>> 4 files changed, 193 insertions(+), 51 deletions(-)
Can you refresh against latest linus master? I will apply then
prev parent reply other threads:[~2022-05-31 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 6:37 [PATCH v3 0/4] KVM: s390: selftests: Provide TAP output in tests Thomas Huth
2022-04-29 6:37 ` [PATCH v3 1/4] KVM: s390: selftests: Use TAP interface in the memop test Thomas Huth
2022-04-29 6:37 ` [PATCH v3 2/4] KVM: s390: selftests: Use TAP interface in the sync_regs test Thomas Huth
2022-04-29 6:37 ` [PATCH v3 3/4] KVM: s390: selftests: Use TAP interface in the tprot test Thomas Huth
2022-04-29 6:37 ` [PATCH v3 4/4] KVM: s390: selftests: Use TAP interface in the reset test Thomas Huth
2022-05-31 8:02 ` [PATCH v3 0/4] KVM: s390: selftests: Provide TAP output in tests Thomas Huth
2022-05-31 9:06 ` Christian Borntraeger [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=9b3c88f2-ca23-df23-4a5b-d86b0b38a6aa@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@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=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