From: Francesco Lavra <francescolavra.fl@gmail.com>
To: ashish.kalra@amd.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com, davem@davemloft.net,
herbert@gondor.apana.org.au, hpa@zytor.com, john.allen@amd.com,
kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, michael.roth@amd.com,
mingo@redhat.com, pbonzini@redhat.com, seanjc@google.com,
tglx@linutronix.de, thomas.lendacky@amd.com, x86@kernel.org
Subject: Re: [PATCH v3 2/4] crypto: ccp: Add support for SNP_FEATURE_INFO command
Date: Thu, 24 Apr 2025 16:38:58 +0200 [thread overview]
Message-ID: <7da931d3e045aad6349879c16db9a8bf17aa0d60.camel@gmail.com> (raw)
In-Reply-To: <0ec035a24116dce7c8b2a36a29cf5eed96e0eb52.1745279916.git.ashish.kalra@amd.com>
On 2025-04-22 at 0:24, Ashish Kalra wrote:
> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-
> dev.c
> index b08db412f752..f4f8a8905115 100644
> --- a/drivers/crypto/ccp/sev-dev.c
> +++ b/drivers/crypto/ccp/sev-dev.c
> @@ -232,6 +232,7 @@ static int sev_cmd_buffer_len(int cmd)
> case SEV_CMD_SNP_GUEST_REQUEST: return
> sizeof(struct sev_data_snp_guest_request);
> case SEV_CMD_SNP_CONFIG: return sizeof(struct
> sev_user_data_snp_config);
> case SEV_CMD_SNP_COMMIT: return sizeof(struct
> sev_data_snp_commit);
> + case SEV_CMD_SNP_FEATURE_INFO: return sizeof(struct
> snp_feature_info);
This function is supposed to return the size of the command buffer, so
for this command it should return sizeof(struct
sev_data_snp_feature_info).
> default: return 0;
> }
>
> @@ -1072,6 +1073,50 @@ static void snp_set_hsave_pa(void *arg)
> wrmsrq(MSR_VM_HSAVE_PA, 0);
> }
>
> +static void snp_get_platform_data(void)
> +{
> + struct sev_device *sev = psp_master->sev_data;
> + struct sev_data_snp_feature_info snp_feat_info;
> + struct snp_feature_info *feat_info;
> + struct sev_data_snp_addr buf;
> + int error = 0, rc;
> +
> + if (!cc_platform_has(CC_ATTR_HOST_SEV_SNP))
> + return;
> +
> + /*
> + * The output buffer must be firmware page if SEV-SNP is
> + * initialized.
> + */
> + if (sev->snp_initialized)
> + return;
> +
> + buf.address = __psp_pa(&sev->snp_plat_status);
> + rc = __sev_do_cmd_locked(SEV_CMD_SNP_PLATFORM_STATUS, &buf,
> &error);
> +
> + /*
> + * Do feature discovery of the currently loaded firmware,
> + * and cache feature information from CPUID 0x8000_0024,
> + * sub-function 0.
> + */
> + if (!rc && sev->snp_plat_status.feature_info) {
> + /*
> + * Use dynamically allocated structure for the
> SNP_FEATURE_INFO
> + * command to handle any alignment and page boundary
> check
> + * requirements.
> + */
> + feat_info = kzalloc(sizeof(*feat_info), GFP_KERNEL);
The SEV firmware requires the supplied memory range to not cross a page
boundary, but kzalloc() does not guarantee that the allocated memory
fits this requirement. You need to allocate a larger chunk of memory (2
* sizeof(*feat_info) will be enough), and possibly set
feature_info_paddr to an offset from the start of the allocated memory.
next prev parent reply other threads:[~2025-04-24 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 0:24 [PATCH v3 0/4] Add SEV-SNP CipherTextHiding feature support Ashish Kalra
2025-04-22 0:24 ` [PATCH v3 1/4] crypto: ccp: New bit-field definitions for SNP_PLATFORM_STATUS command Ashish Kalra
2025-04-22 0:24 ` [PATCH v3 2/4] crypto: ccp: Add support for SNP_FEATURE_INFO command Ashish Kalra
2025-04-23 21:21 ` Tom Lendacky
2025-04-24 14:38 ` Francesco Lavra [this message]
2025-04-22 0:25 ` [PATCH v3 3/4] crypto: ccp: Add support to enable CipherTextHiding on SNP_INIT_EX Ashish Kalra
2025-04-23 22:19 ` Tom Lendacky
2025-05-07 5:44 ` kernel test robot
2025-04-22 0:25 ` [PATCH v3 4/4] KVM: SVM: Add SEV-SNP CipherTextHiding support Ashish Kalra
2025-04-23 21:15 ` Sean Christopherson
2025-04-25 19:46 ` Kalra, Ashish
2025-04-26 0:00 ` 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=7da931d3e045aad6349879c16db9a8bf17aa0d60.camel@gmail.com \
--to=francescolavra.fl@gmail.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=hpa@zytor.com \
--cc=john.allen@amd.com \
--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=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox