From: Paolo Bonzini <pbonzini@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>, kvm@vger.kernel.org
Cc: shuah@kernel.org, tglx@linutronix.de, thuth@redhat.com,
sean.j.christopherson@intel.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] kvm: selftests: Add TEST_FAIL macro
Date: Thu, 5 Mar 2020 18:28:53 +0100 [thread overview]
Message-ID: <e7bacea1-6964-aeb2-633e-371ad1231881@redhat.com> (raw)
In-Reply-To: <20200305172532.9360-1-wainersm@redhat.com>
On 05/03/20 18:25, Wainer dos Santos Moschetta wrote:
> The following patch's commit message is self-explanatory about this proposal.
>
> I adjusted to use TEST_FAIL only a few source files, in reality it will
> need to change all the ones listed below. I will proceed with the
> adjustments if this new macro idea is accepted.
>
> $ find . -type f -name "*.c" -exec grep -l "TEST_ASSERT(false" {} \;
> ./lib/kvm_util.c
> ./lib/io.c
> ./lib/x86_64/processor.c
> ./lib/aarch64/ucall.c
> ./lib/aarch64/processor.c
> ./x86_64/vmx_dirty_log_test.c
> ./x86_64/state_test.c
> ./x86_64/vmx_tsc_adjust_test.c
> ./x86_64/svm_vmcall_test.c
> ./x86_64/evmcs_test.c
> ./x86_64/vmx_close_while_nested_test.c
>
> Wainer dos Santos Moschetta (1):
> kvm: selftests: Add TEST_FAIL macro
>
> tools/testing/selftests/kvm/dirty_log_test.c | 7 +++----
> tools/testing/selftests/kvm/include/test_util.h | 3 +++
> tools/testing/selftests/kvm/x86_64/cr4_cpuid_sync_test.c | 4 ++--
> 3 files changed, 8 insertions(+), 6 deletions(-)
>
Yes, why not.
Paolo
prev parent reply other threads:[~2020-03-05 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 17:25 [RFC PATCH 0/1] kvm: selftests: Add TEST_FAIL macro Wainer dos Santos Moschetta
2020-03-05 17:25 ` [RFC PATCH 1/1] " Wainer dos Santos Moschetta
2020-03-05 17:28 ` Paolo Bonzini [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=e7bacea1-6964-aeb2-633e-371ad1231881@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=wainersm@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