From: David Hildenbrand <david@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v2 2/3] KVM: VMX: Fix enable VPID even if INVVPID is not exposed in vmx capability
Date: Tue, 21 Mar 2017 10:01:17 +0100 [thread overview]
Message-ID: <1e4698b6-35fb-aa74-8a6a-fa7a3fd862d4@redhat.com> (raw)
In-Reply-To: <CANRm+CxJuYvMbrx72qCGKAdURZ+M=hm+oKXEF7K-g=u-mmTURw@mail.gmail.com>
> The same as cpu_has_vmx_ept_4levels().
>
>>
>>> enable_vpid = 0;
>>> +
>>
>> unrelated change
>
> To make the vpid codes more clear. Please refer to other callees in
> hardware_setup().
I was talking about the added empty line. This is unrelated to the patch
you're posting.
--
Thanks,
David
next prev parent reply other threads:[~2017-03-21 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 4:18 [PATCH v2 1/3] KVM: nVMX: Fix nested VPID vmx exec control Wanpeng Li
2017-03-21 4:18 ` [PATCH v2 2/3] KVM: VMX: Fix enable VPID even if INVVPID is not exposed in vmx capability Wanpeng Li
2017-03-21 8:50 ` David Hildenbrand
2017-03-21 8:58 ` Wanpeng Li
2017-03-21 9:01 ` David Hildenbrand [this message]
2017-03-21 9:05 ` Wanpeng Li
2017-03-21 9:15 ` David Hildenbrand
2017-03-21 16:19 ` Paolo Bonzini
2017-03-21 4:18 ` [PATCH v2 3/3] KVM: x86: correct async page present tracepoint Wanpeng Li
2017-03-21 8:57 ` David Hildenbrand
2017-03-21 16:19 ` [PATCH v2 1/3] KVM: nVMX: Fix nested VPID vmx exec control Paolo Bonzini
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=1e4698b6-35fb-aa74-8a6a-fa7a3fd862d4@redhat.com \
--to=david@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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
all inboxes | Powered by JetHome®