From: Paolo Bonzini <pbonzini@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>, Jim Mattson <jmattson@google.com>
Cc: kvm list <kvm@vger.kernel.org>,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: [kvm-unit-tests PATCH 1/2] x86: nVMX: Use #DB in nmi and intr tests
Date: Mon, 20 May 2019 17:52:41 +0200 [thread overview]
Message-ID: <76ffb0ca-c007-05c4-7bef-5f72f03a7a4e@redhat.com> (raw)
In-Reply-To: <7B8B0BFD-3D85-4062-9F44-7BA8AC7F9DAE@gmail.com>
On 09/05/19 01:35, Nadav Amit wrote:
> I just hope that this support would convince you, and others, to prefer
> (when possible) kvm-unit-tests over the selftest environment.
kvm-unit-tests are not superseded by selftests; selftests are mostly
meant to test the KVM API. While they are more easily debuggable than
kvm-unit-tests, the benefit is not big enough to justify the effort of
rewriting everything.
Furthermore, being able to run kvm-unit-tests on bare metal is useful,
even if it's not something that people commonly do, and consistent with
KVM's design of not departing radically for what bare metal does.
Thanks,
Paolo
next prev parent reply other threads:[~2019-05-20 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 10:27 [kvm-unit-tests PATCH 0/2] x86: nVMX: Fix NMI/INTR-window tests Nadav Amit
2019-05-08 10:27 ` [kvm-unit-tests PATCH 1/2] x86: nVMX: Use #DB in nmi and intr tests Nadav Amit
2019-05-08 23:11 ` Jim Mattson
2019-05-08 23:35 ` Nadav Amit
2019-05-20 15:52 ` Paolo Bonzini [this message]
2019-05-20 16:39 ` Nadav Amit
2019-05-20 17:21 ` Paolo Bonzini
2019-05-08 10:27 ` [kvm-unit-tests PATCH 2/2] x86: nVMX: Set guest as active after NMI/INTR-window tests Nadav Amit
2019-05-08 23:21 ` Jim Mattson
2019-05-08 23:38 ` Nadav Amit
2019-05-09 20:48 ` Sean Christopherson
2019-05-09 20:32 ` Sean Christopherson
2019-05-09 21:29 ` Nadav Amit
2019-05-15 16:57 ` Sean Christopherson
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=76ffb0ca-c007-05c4-7bef-5f72f03a7a4e@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=sean.j.christopherson@intel.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