From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, jejb@linux.ibm.com
Cc: dovmurik@linux.vnet.ibm.com, Dov.Murik1@il.ibm.com,
ashish.kalra@amd.com, brijesh.singh@amd.com, tobin@ibm.com,
david.kaplan@amd.com, jon.grimm@amd.com, thomas.lendacky@amd.com,
frankeh@us.ibm.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/2] Update SevSecret API to work for TDX
Date: Fri, 18 Dec 2020 11:49:50 +0100 [thread overview]
Message-ID: <67c62cdc-2362-b480-f476-506c66a2438e@redhat.com> (raw)
In-Reply-To: <20201216014146.2229-1-jejb@linux.ibm.com>
On 12/16/20 02:41, James Bottomley wrote:
> This patch series changes the EFI configuration table information
> which is queried by the bootloader to make it more compatible with
> Intel TDX. The first patch changes the ABI to make the table contain
> two 64 bit integers instead of two 32 bit ones. The second patch is a
> cosmetic one to change the names of the GUIDs and tables to have a
> confidential computing prefix instead of a SEV Launch one.
>
> The first patch *must* be applied before the next stable tag to avoid
> ABI breakage. The second is purely cosmetic and doesn't change the
> code output.
>
> Ultimately there will still need to be a TDX collector for the secret,
> which would feed the value into the SecretDxe, but these changes
> should ensure that no further changes would be required by the secret
> consumers.
>
> James
>
> ---
>
> James Bottomley (2):
> OvmfPkg: Change SEV Launch Secret API to be UINT64 for base and size
> OvmfPkg/AmdSev/SecretDxe: make secret location naming generic
>
> OvmfPkg/OvmfPkg.dec | 2 +-
> OvmfPkg/AmdSev/SecretDxe/SecretDxe.inf | 2 +-
> ...aunchSecret.h => ConfidentialComputingSecret.h} | 14 +++++++-------
> OvmfPkg/AmdSev/SecretDxe/SecretDxe.c | 6 +++---
> 4 files changed, 12 insertions(+), 12 deletions(-)
> rename OvmfPkg/Include/Guid/{SevLaunchSecret.h => ConfidentialComputingSecret.h} (65%)
>
Merged as commit range c487970ac89d..96201ae7bf97, via
<https://github.com/tianocore/edk2/pull/1235>.
Thanks
Laszlo
prev parent reply other threads:[~2020-12-18 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 1:41 [PATCH 0/2] Update SevSecret API to work for TDX James Bottomley
2020-12-16 1:41 ` [PATCH 1/2] OvmfPkg: Change SEV Launch Secret API to be UINT64 for base and size James Bottomley
2020-12-16 1:41 ` [PATCH 2/2] OvmfPkg/AmdSev/SecretDxe: make secret location naming generic James Bottomley
2020-12-16 8:27 ` Dov Murik
2020-12-16 16:53 ` James Bottomley
2020-12-17 0:25 ` Yao, Jiewen
2020-12-16 1:55 ` [PATCH 0/2] Update SevSecret API to work for TDX Yao, Jiewen
2020-12-17 18:43 ` [edk2-devel] " Laszlo Ersek
2020-12-17 19:23 ` Laszlo Ersek
2020-12-17 20:00 ` Laszlo Ersek
2020-12-18 10:49 ` Laszlo Ersek [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=67c62cdc-2362-b480-f476-506c66a2438e@redhat.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