From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm list <kvm@vger.kernel.org>, Liran Alon <liran.alon@oracle.com>
Subject: Re: [PATCH] kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field
Date: Tue, 10 Dec 2019 09:39:21 +0100 [thread overview]
Message-ID: <d1ff0d0a-a7b1-970c-3755-559f89a90713@redhat.com> (raw)
In-Reply-To: <CALMp9eRag2YFfK-2y-e12NdP+EE068nC+Sv_=BVtBdPXV-FE7Q@mail.gmail.com>
On 10/12/19 00:34, Jim Mattson wrote:
> On Mon, Dec 9, 2019 at 8:12 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 05/12/19 22:30, Jim Mattson wrote:
>>>> I'll put one together, along with a test that shows the current
>>>> priority inversion between read-only and unsupported VMCS fields.
>>> I can't figure out how to clear IA32_VMX_MISC[bit 29] in qemu, so I'm
>>> going to add the test to tools/testing/selftests/kvm instead.
>>>
>>
>> With the next version of QEMU it will be "-cpu
>> host,-vmx-vmwrite-vmexit-fields".
>
> Or, presumably, -cpu Westmere?
Yes, more precisely -cpu Westmere,+vmx because nested is still not the
default for named CPU models.
Paolo
prev parent reply other threads:[~2019-12-10 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 21:40 [PATCH] kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field Jim Mattson
2019-12-05 11:28 ` Vitaly Kuznetsov
2019-12-05 11:45 ` Paolo Bonzini
2019-12-05 13:11 ` Jim Mattson
2019-12-05 21:30 ` Jim Mattson
2019-12-05 21:54 ` Liran Alon
2019-12-05 22:11 ` Jim Mattson
2019-12-09 15:28 ` Nadav Amit
2019-12-09 22:58 ` Liran Alon
2019-12-10 22:22 ` Nadav Amit
2019-12-09 16:12 ` Paolo Bonzini
2019-12-09 23:34 ` Jim Mattson
2019-12-10 8:39 ` 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=d1ff0d0a-a7b1-970c-3755-559f89a90713@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.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;
as well as URLs for NNTP newsgroup(s).