[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f9eac75ac315070db68a76454e9430ed11398ccf.camel@intel.com>
Date: Thu, 20 Apr 2023 10:55:22 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "Christopherson,, Sean" <seanjc@...gle.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] KVM: VMX: Don't rely _only_ on CPUID to enforce XCR0
restrictions for ECREATE
> >
> > Oooh, right. It's not that FP+SSE are always allowed, it's that FP+SSE must always
> > be _set_. So this?
> >
> > xfrm & ~(vcpu->arch.guest_supported_xcr0 | XFEATURE_MASK_FPSSE) ||
> > (xfrm & XFEATURE_MASK_FPSSE) != XFEATURE_MASK_FPSSE
>
> Looks good.
>
> I'll try to get some test done with this code change.
>
Tested this series with your above code change by running simple SGX app in the
guest.
For this particular case, tested with ECREATE with xfrm = 0x1 in the guest, and
guest can receive #GP.
So for the entire series:
Reviewed-by: Kai Huang <kai.huang@...el.com>
Tested-by: Kai Huang <kai.huang@...el.com>
>
Powered by blists - more mailing lists