[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108080515.GAZ34xuwMjbrSYFcHN@fat_crate.local>
Date: Wed, 8 Jan 2025 09:05:15 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Nikunj A. Dadhania" <nikunj@....com>
Cc: Tom Lendacky <thomas.lendacky@....com>, linux-kernel@...r.kernel.org,
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, francescolavra.fl@...il.com
Subject: Re: [PATCH v16 05/13] x86/sev: Add Secure TSC support for SNP guests
On Wed, Jan 08, 2025 at 01:17:11PM +0530, Nikunj A. Dadhania wrote:
> diff --git a/arch/x86/coco/sev/core.c b/arch/x86/coco/sev/core.c
> index 00a0ac3baab7..763cfeb65b2f 100644
> --- a/arch/x86/coco/sev/core.c
> +++ b/arch/x86/coco/sev/core.c
> @@ -3218,7 +3218,8 @@ static int __init snp_get_tsc_info(void)
>
> void __init snp_secure_tsc_prepare(void)
> {
> - if (!cc_platform_has(CC_ATTR_GUEST_SNP_SECURE_TSC))
> + if (!cc_platform_has(CC_ATTR_GUEST_SEV_SNP) ||
> + !cc_platform_has(CC_ATTR_GUEST_SNP_SECURE_TSC))
So how is moving the CC_ATTR_GUEST_SEV_SNP check here make any sense?
I simply zapped the MSR_AMD64_SEV_SNP_ENABLED check above locally.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists