From: Sean Christopherson <seanjc@google.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-crypto@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH v4 2/4] crypto: ccp - Add an API to return the supported SEV-SNP policy bits
Date: Thu, 13 Nov 2025 10:52:03 -0800 [thread overview]
Message-ID: <aRYo05KMsaNdj59U@google.com> (raw)
In-Reply-To: <e3f711366ddc22e3dd215c987fd2e28dc1c07f54.1761593632.git.thomas.lendacky@amd.com>
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@amd.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
next prev parent reply other threads:[~2025-11-13 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:33 [PATCH v4 0/4] SEV-SNP guest policy bit support updates Tom Lendacky
2025-10-27 19:33 ` [PATCH v4 1/4] KVM: SEV: Consolidate the SEV policy bits in a single header file Tom Lendacky
2025-10-27 19:33 ` [PATCH v4 2/4] crypto: ccp - Add an API to return the supported SEV-SNP policy bits Tom Lendacky
2025-11-13 18:52 ` Sean Christopherson [this message]
2025-11-13 18:58 ` Tom Lendacky
2025-11-13 21:15 ` Sean Christopherson
2025-11-14 9:37 ` Herbert Xu
2025-10-27 19:33 ` [PATCH v4 3/4] KVM: SEV: Publish " Tom Lendacky
2025-10-27 19:33 ` [PATCH v4 4/4] KVM: SEV: Add known " Tom Lendacky
2025-11-13 18:54 ` [PATCH v4 0/4] SEV-SNP guest policy bit support updates Sean Christopherson
2025-11-18 23:27 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aRYo05KMsaNdj59U@google.com \
--to=seanjc@google.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.