[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59084476-e210-4392-b73b-1038a2956e31@intel.com>
Date: Tue, 29 Oct 2024 23:14:29 +0800
From: Xiaoyao Li <xiaoyao.li@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: "Nikunj A. Dadhania" <nikunj@....com>, linux-kernel@...r.kernel.org,
thomas.lendacky@....com, x86@...nel.org, kvm@...r.kernel.org,
mingo@...hat.com, tglx@...utronix.de, dave.hansen@...ux.intel.com,
pgonda@...gle.com, seanjc@...gle.com, pbonzini@...hat.com
Subject: Re: [PATCH v14 03/13] x86/sev: Add Secure TSC support for SNP guests
On 10/29/2024 11:03 PM, Borislav Petkov wrote:
> On Tue, Oct 29, 2024 at 10:50:18PM +0800, Xiaoyao Li wrote:
>> I meant the starter to add SNP guest specific feature initialization code in
>> somewhat in proper place.
>
> https://lore.kernel.org/r/20241029144948.GIZyD2DBjyg6FBLdo4@fat_crate.local
>
> IOW, I don't think we really have a "proper" place yet.
Then why can't we create one for it?
> There are vendor
> checks all over the memory encryption code for different reasons.
But they are at least related to memory encryption, I think.
However, how secure TSC related to memory encryption?
Powered by blists - more mailing lists