[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0dc77b4b-1f8d-f21c-303b-3ea6d5b978db@intel.com>
Date: Thu, 4 May 2023 09:11:08 +0800
From: "Yang, Weijiang" <weijiang.yang@...el.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"john.allen@....com" <john.allen@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: [PATCH v2 21/21] KVM:x86: Support CET supervisor shadow stack MSR
access
On 5/4/2023 1:06 AM, Edgecombe, Rick P wrote:
> On Fri, 2023-04-21 at 09:46 -0400, Yang Weijiang wrote:
>> @@ -2471,6 +2495,12 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu,
>> struct msr_data *msr_info)
>> else
>> kvm_set_xsave_msr(msr_info);
>> break;
>> + case MSR_IA32_PL0_SSP ... MSR_IA32_PL2_SSP:
>> + case MSR_IA32_INT_SSP_TAB:
>> + if (!cet_is_msr_accessible(vcpu, msr_info))
>> + return 1;
>> + kvm_set_xsave_msr(msr_info);
>> + break;
> These are supposed to be canonical too, right?
Yes, I'll add check in next version, thanks!
Powered by blists - more mailing lists