[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3b2fba8-9356-4f69-9214-8c3723d6c919@amd.com>
Date: Wed, 9 Oct 2024 16:30:12 +0530
From: Neeraj Upadhyay <Neeraj.Upadhyay@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
dave.hansen@...ux.intel.com, Thomas.Lendacky@....com, nikunj@....com,
Santosh.Shukla@....com, Vasant.Hegde@....com, Suravee.Suthikulpanit@....com,
David.Kaplan@....com, x86@...nel.org, hpa@...or.com, peterz@...radead.org,
seanjc@...gle.com, pbonzini@...hat.com, kvm@...r.kernel.org
Subject: Re: [RFC 01/14] x86/apic: Add new driver for Secure AVIC
On 10/9/2024 4:08 PM, Borislav Petkov wrote:
> On Wed, Oct 09, 2024 at 11:31:07AM +0530, Neeraj Upadhyay wrote:
>> Before this patch, if hypervisor enables Secure AVIC (reported in sev_status), guest would
>> terminate in snp_check_features().
>
> We want the guest to terminate at this patch too.
>
If I understand it correctly, you are fine with adding MSR_AMD64_SNP_SECURE_AVIC_ENABLED
to SNP_FEATURES_IMPL_REQ in this patch.
> The only case where the guest should not terminate is when the *full* sAVIC
> support is in. I.e., at patch 14.
>
Got it. This version of the patch series is following that.
- Neeraj
Powered by blists - more mailing lists