From: linmiaohe <linmiaohe@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"sean.j.christopherson@intel.com"
<sean.j.christopherson@intel.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH] KVM: nVMX: set rflags to specify success in handle_invvpid() default case
Date: Thu, 23 Jan 2020 09:36:30 +0000 [thread overview]
Message-ID: <a3eb519e5831459db1c926776ad97cca@huawei.com> (raw)
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 23/01/20 09:55, Vitaly Kuznetsov wrote:
> > Your patch seems to do the right thing, however, I started wondering
> > if
> > WARN_ON_ONCE() is the right thing to do. SDM says that "If an
> > unsupported INVVPID type is specified, the instruction fails." and
> > this is similar to INVEPT and I decided to check what handle_invept()
> > does. Well, it does BUG_ON().
> >
> > Are we doing the right thing in any of these cases?
>
> Yes, both INVEPT and INVVPID catch this earlier.
>
> For INVEPT:
>
> types = (vmx->nested.msrs.ept_caps >> VMX_EPT_EXTENT_SHIFT) & 6;
>
> if (type >= 32 || !(types & (1 << type)))
> return nested_vmx_failValid(vcpu,
> VMXERR_INVALID_OPERAND_TO_INVEPT_INVVPID);
>
>
>
> For INVVPID:
>
> types = (vmx->nested.msrs.vpid_caps &
> VMX_VPID_EXTENT_SUPPORTED_MASK) >> 8;
>
> if (type >= 32 || !(types & (1 << type)))
> return nested_vmx_failValid(vcpu,
> VMXERR_INVALID_OPERAND_TO_INVEPT_INVVPID);
>
> So I'm leaning towards not applying Miaohe's patch. Happy Mouse Year to everyone, here is an ASCII art (except for one Unicode character) mouse:
>
>
> __()()
> / o)
> ~~~~\_,__,_>°
>
> Thanks,
Yes, it seems my patch is meaningless. And thanks for both of your review and reply.
Happy Mouse Year and I catch a mickey mouse:
###########
############### __-----__ ##
################## ### \ ####
################## #### # \ # ##
#################### \~~\ \ ,##",
################# /~~\ \## \ \" :
############### \ \ \##" / :
####### \### \ / :
############# \###/ :
######## :
###### __ :
#### /\ /
############ ### \\______________/|
################## \ __ / /
####################\__ \ \---\,/ /
################### \ \_____/ /
################# \_________/
###############
###########
Thanks both again.
next reply other threads:[~2020-01-23 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 9:36 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-04 1:06 [PATCH] KVM: nVMX: set rflags to specify success in handle_invvpid() default case linmiaohe
2020-02-03 3:29 linmiaohe
2020-02-03 9:48 ` Vitaly Kuznetsov
2020-01-23 3:14 linmiaohe
2020-01-23 8:55 ` Vitaly Kuznetsov
2020-01-23 9:23 ` Paolo Bonzini
2020-01-23 9:45 ` Vitaly Kuznetsov
2020-01-23 9:54 ` Paolo Bonzini
2020-01-23 18:22 ` Jim Mattson
2020-01-23 23:01 ` Sean Christopherson
2020-01-24 10:53 ` Vitaly Kuznetsov
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=a3eb519e5831459db1c926776ad97cca@huawei.com \
--to=linmiaohe@huawei.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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