linux-kernel - Re: [PATCH v3 0/4] KVM: s390: selftests: Provide TAP output in tests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9b3c88f2-ca23-df23-4a5b-d86b0b38a6aa@linux.ibm.com>
Date:   Tue, 31 May 2022 11:06:48 +0200
From:   Christian Borntraeger <borntraeger@...ux.ibm.com>
To:     Thomas Huth <thuth@...hat.com>, kvm@...r.kernel.org,
        Janosch Frank <frankja@...ux.ibm.com>,
        Claudio Imbrenda <imbrenda@...ux.ibm.com>
Cc:     linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
        David Hildenbrand <david@...hat.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Shuah Khan <shuah@...nel.org>,
        Janis Schoetterl-Glausch <scgl@...ux.ibm.com>,
        linux-s390@...r.kernel.org
Subject: Re: [PATCH v3 0/4] KVM: s390: selftests: Provide TAP output in tests



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