[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4af95c25-6dd7-924a-c17e-bee4d73e9728@amd.com>
Date: Mon, 16 Sep 2024 10:23:13 +0530
From: "Nikunj A. Dadhania" <nikunj@....com>
To: Tom Lendacky <thomas.lendacky@....com>, linux-kernel@...r.kernel.org,
bp@...en8.de, x86@...nel.org, kvm@...r.kernel.org
Cc: mingo@...hat.com, tglx@...utronix.de, dave.hansen@...ux.intel.com,
pgonda@...gle.com, seanjc@...gle.com, pbonzini@...hat.com
Subject: Re: [PATCH v11 13/20] x86/cc: Add CC_ATTR_GUEST_SECURE_TSC
On 9/13/2024 8:51 PM, Tom Lendacky wrote:
> On 7/31/24 10:08, Nikunj A Dadhania wrote:
>> @@ -88,6 +88,14 @@ enum cc_attr {
>> * enabled to run SEV-SNP guests.
>> */
>> CC_ATTR_HOST_SEV_SNP,
>> +
>> + /**
>> + * @CC_ATTR_GUEST_SECURE_TSC: Secure TSC is active.
>> + *
>> + * The platform/OS is running as a guest/virtual machine and actively
>> + * using AMD SEV-SNP Secure TSC feature.
>> + */
>> + CC_ATTR_GUEST_SECURE_TSC,
>
> If this is specifically used for the AMD feature, as opposed to a generic
> "does your system have a secure TSC", then it should probably be
> CC_ATTR_GUEST_SNP_SECURE_TSC or CC_ATTR_GUEST_SEV_SNP_SECURE_TSC.
Sure, let me rename it to CC_ATTR_GUEST_SNP_SECURE_TSC.
Regards
Nikunj
Powered by blists - more mailing lists