From: Michael Roth <michael.roth@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: <devel@edk2.groups.io>
Subject: Re: [PATCH] OvmfPkg/AmdSevDxe: Update ConfidentialComputing blob struct definition
Date: Fri, 13 May 2022 08:52:14 -0500 [thread overview]
Message-ID: <20220513135214.zaax6pmhwuoxqiqf@amd.com> (raw)
In-Reply-To: <14a3ed39-163c-d7a4-d4c4-04afa522f742@amd.com>
On Fri, May 13, 2022 at 08:32:38AM -0500, Tom Lendacky wrote:
> On 5/13/22 08:22, Michael Roth wrote:
> > The Confidential Computing blob defined here is intended to match the
> > definition defined by linux guest kernel. Previously, both definitions
> > relied on natural alignment, but that relies on both OVMF and kernel
> > being compiled as 64-bit. While there aren't currently any plans to
> > enable SNP support for 32-bit compilations, the kernel definition has
> > since been updated to use explicit padding/reserved fields to avoid
> > this dependency. Update OVMF to match that definition.
> >
> > No functional changes (for currently-supported environments, at least).
> >
> > Signed-off-by: Michael Roth <michael.roth@amd.com>
>
> Minor nit comment below that can be ignored if desired.
>
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
>
> > ---
> > OvmfPkg/AmdSevDxe/AmdSevDxe.c | 2 ++
> > OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h | 6 ++++--
> > 2 files changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/OvmfPkg/AmdSevDxe/AmdSevDxe.c b/OvmfPkg/AmdSevDxe/AmdSevDxe.c
> > index 662d3c4ccb..ee6d2528d9 100644
> > --- a/OvmfPkg/AmdSevDxe/AmdSevDxe.c
> > +++ b/OvmfPkg/AmdSevDxe/AmdSevDxe.c
> > @@ -27,8 +27,10 @@ STATIC CONFIDENTIAL_COMPUTING_SNP_BLOB_LOCATION mSnpBootDxeTable = {
> > 0,
> > (UINT64)(UINTN)FixedPcdGet32 (PcdOvmfSnpSecretsBase),
> > FixedPcdGet32 (PcdOvmfSnpSecretsSize),
> > + 0,
> > (UINT64)(UINTN)FixedPcdGet32 (PcdOvmfCpuidBase),
> > FixedPcdGet32 (PcdOvmfCpuidSize),
> > + 0,
> > };
> > EFI_STATUS
> > diff --git a/OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h b/OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h
> > index b328310fd0..83620e31b8 100644
> > --- a/OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h
> > +++ b/OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h
> > @@ -18,14 +18,16 @@
> > { 0x85, 0x54, 0x93, 0xd7, 0x77, 0x91, 0x2d, 0x42 }, \
> > }
> > -typedef struct {
> > +typedef PACKED struct {
> > UINT32 Header;
> > UINT16 Version;
> > - UINT16 Reserved1;
> > + UINT16 Reserved;
>
> Not to be picky, but I would have left this as Reserved1 and then made the
> below entries Reserved2 and Reserved3.
Hi Tom,
I updated those to match how the reserved fields are numbered in the
kernel since it seemed like it could cause confusion otherwise. I should
have noted that in the commit log though as it's a somewhat unrelated
change.
Thanks!
-Mike
>
> Thanks,
> Tom
>
> > UINT64 SecretsPhysicalAddress;
> > UINT32 SecretsSize;
> > + UINT32 Reserved1;
> > UINT64 CpuidPhysicalAddress;
> > UINT32 CpuidLSize;
> > + UINT32 Reserved2;
> > } CONFIDENTIAL_COMPUTING_SNP_BLOB_LOCATION;
> > extern EFI_GUID gConfidentialComputingSevSnpBlobGuid;
prev parent reply other threads:[~2022-05-13 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 13:22 [PATCH] OvmfPkg/AmdSevDxe: Update ConfidentialComputing blob struct definition Michael Roth
2022-05-13 13:32 ` Lendacky, Thomas
2022-05-13 13:52 ` Michael Roth [this message]
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-list 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=20220513135214.zaax6pmhwuoxqiqf@amd.com \
--to=devel@edk2.groups.io \
/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