[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e9d3d9d-6541-41ed-994c-04415962a7da@amd.com>
Date: Thu, 13 Nov 2025 12:58:39 -0600
From: Tom Lendacky <thomas.lendacky@....com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, x86@...nel.org,
linux-crypto@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
Michael Roth <michael.roth@....com>, Ashish Kalra <ashish.kalra@....com>,
Herbert Xu <herbert@...dor.apana.org.au>, David Miller <davem@...emloft.net>
Subject: Re: [PATCH v4 2/4] crypto: ccp - Add an API to return the supported
SEV-SNP policy bits
On 11/13/25 12:52, Sean Christopherson wrote:
> On Mon, Oct 27, 2025, Tom Lendacky wrote:
>> Supported policy bits are dependent on the level of SEV firmware that is
>> currently running. Create an API to return the supported policy bits for
>> the current level of firmware.
>>
>> Signed-off-by: Tom Lendacky <thomas.lendacky@....com>
>> ---
>
> ...
>
>> @@ -1014,6 +1031,7 @@ void *snp_alloc_firmware_page(gfp_t mask);
>> void snp_free_firmware_page(void *addr);
>> void sev_platform_shutdown(void);
>> bool sev_is_snp_ciphertext_hiding_supported(void);
>> +u64 sev_get_snp_policy_bits(void);
>>
>> #else /* !CONFIG_CRYPTO_DEV_SP_PSP */
>>
>> @@ -1052,6 +1070,8 @@ static inline void sev_platform_shutdown(void) { }
>>
>> static inline bool sev_is_snp_ciphertext_hiding_supported(void) { return false; }
>>
>> +static inline u64 sev_get_snp_policy_bits(void) { return 0; }
>
> As called out in the RFC[*], this stub is unnecesary.
>
> [*] https://lore.kernel.org/all/aMHP5EO-ucJGdHXz@google.com
Ah, sorry, missed that one. Do you want a fix up or do you want to handle it?
Thanks,
Tom
Powered by blists - more mailing lists