From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: Nadav Amit <nadav.amit@gmail.com>,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
jmattson@google.com
Subject: Re: [PATCH] kvm-unit-test: nVMX: Test Selector and Base Address fields of Guest Segment Registers on vmentry of nested guests
Date: Wed, 11 Mar 2020 16:30:05 -0700 [thread overview]
Message-ID: <20200311233005.GN21852@linux.intel.com> (raw)
In-Reply-To: <e87a88de-f1cd-0bde-48a8-c66b915435de@oracle.com>
On Wed, Mar 11, 2020 at 11:22:13PM +0000, Liran Alon wrote:
>
> On 12/03/2020 1:12, Sean Christopherson wrote:
> >On Thu, Mar 12, 2020 at 12:54:05AM +0200, Liran Alon wrote:
> >>Of course it was best if Intel would have shared their unit-tests for CPU
> >>functionality (Sean? I'm looking at you :P), but I am not aware that they
> >>did.
> >Only in my dreams :-) I would love to open source some of Intel's
> >validation tools so that they could be adapted to hammer KVM, but it'll
> >never happen for a variety of reasons.
>
> I hope then you at least built a setup internally at Intel that runs these
> test suites on top of KVM to find bugs. :)
It's on my wish list.
> It would also be nice of Intel to even setup this internally on top of other
> common hypervisors (e.g. Hyper-V, VMware) and report bugs to vendors.
>
> -Liran
>
>
next prev parent reply other threads:[~2020-03-11 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 22:51 [PATCH] kvm-unit-test: nVMX: Test Selector and Base Address fields of Guest Segment registers Krish Sadhukhan
2020-03-10 22:51 ` [PATCH] kvm-unit-test: nVMX: Test Selector and Base Address fields of Guest Segment Registers on vmentry of nested guests Krish Sadhukhan
2020-03-11 15:05 ` Sean Christopherson
2020-03-11 15:19 ` Sean Christopherson
2020-03-11 20:38 ` Krish Sadhukhan
2020-03-11 21:46 ` Sean Christopherson
2020-03-11 21:53 ` Nadav Amit
2020-03-11 22:54 ` Liran Alon
2020-03-11 23:12 ` Sean Christopherson
2020-03-11 23:21 ` Nadav Amit
2020-03-11 23:25 ` Sean Christopherson
2020-03-11 23:35 ` Nadav Amit
2020-03-11 23:22 ` Liran Alon
2020-03-11 23:30 ` Sean Christopherson [this message]
2020-03-10 23:51 ` [PATCH] kvm-unit-test: nVMX: Test Selector and Base Address fields of Guest Segment registers Jim Mattson
[not found] ` <20200311152459.GD21852@linux.intel.com>
2020-03-12 23:37 ` Krish Sadhukhan
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=20200311233005.GN21852@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.