From: Nadav Amit <nadav.amit@gmail.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Liran Alon <liran.alon@oracle.com>,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <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:35:37 -0700 [thread overview]
Message-ID: <E6A6C555-8750-41E4-AD34-68EB0769C4BE@gmail.com> (raw)
In-Reply-To: <20200311232550.GM21852@linux.intel.com>
> On Mar 11, 2020, at 4:25 PM, Sean Christopherson <sean.j.christopherson@intel.com> wrote:
>
> On Wed, Mar 11, 2020 at 04:21:08PM -0700, Nadav Amit wrote:
>>> On Mar 11, 2020, at 4:12 PM, Sean Christopherson <sean.j.christopherson@intel.com> 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.
>>
>> FYI: In 2014 I ran Intel’s fuzzing-tool (Cafe) to test KVM and found (and
>> fixed) ~100 bugs. And I did not even test nested virtualization…
>
> Heh, I worked on Cafe for 6+ years :-)
Well, I was working on its predecessor, Janus, for 5 years…
next prev parent reply other threads:[~2020-03-11 23:35 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 [this message]
2020-03-11 23:22 ` Liran Alon
2020-03-11 23:30 ` Sean Christopherson
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=E6A6C555-8750-41E4-AD34-68EB0769C4BE@gmail.com \
--to=nadav.amit@gmail.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.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 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.