From: "Laszlo Ersek" <lersek@redhat.com>
To: jejb@linux.ibm.com, devel@edk2.groups.io
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>
Subject: Re: [edk2-devel] [PATCH v3 0/6] SEV Encrypted Boot for Ovmf
Date: Fri, 4 Dec 2020 03:01:11 +0100 [thread overview]
Message-ID: <a968365d-e595-7005-16b7-53a0dad22b3d@redhat.com> (raw)
In-Reply-To: <18bbe7d1-a51a-647e-d05a-73e5465d31cc@redhat.com>
On 12/04/20 02:55, Laszlo Ersek wrote:
> I will send a short patch series to add the exceptions, and once
> that's upstream, we *will* merge this (v3) series.
BTW the tweaks I added on top of your v3, in
<https://github.com/tianocore/edk2/pull/1175>, are as follows (git
range-diff output):
> 1: 4020c20b2342 ! 1: b96494ad75db OvmfPkg/ResetVector: convert SEV-ES Reset Block structure to be GUIDed
> @@ -8,8 +8,9 @@
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> -
> Message-Id: <20201130202819.3910-2-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> diff --git a/OvmfPkg/ResetVector/Ia16/ResetVectorVtf0.asm b/OvmfPkg/ResetVector/Ia16/ResetVectorVtf0.asm
> --- a/OvmfPkg/ResetVector/Ia16/ResetVectorVtf0.asm
> 2: 488fbdbe7689 ! 2: acc8cb13da8d OvmfPkg/Amdsev: Base commit to build encrypted boot specific OVMF
> @@ -11,8 +11,9 @@
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> -
> Message-Id: <20201130202819.3910-3-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> diff --git a/OvmfPkg/AmdSev/AmdSevX64.dsc b/OvmfPkg/AmdSev/AmdSevX64.dsc
> new file mode 100644
> 3: 796ec96e3414 ! 3: b80ce0838781 OvmfPkg/AmdSev: add Grub Firmware Volume Package
> @@ -19,8 +19,10 @@
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> -
> Message-Id: <20201130202819.3910-4-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + [lersek@redhat.com: replace local variable initialization with assignment]
> + Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec
> --- a/OvmfPkg/OvmfPkg.dec
> @@ -779,7 +781,9 @@
> +{
> + EFI_HANDLE Handle;
> + EFI_STATUS Status;
> -+ UINT16 FrontPageTimeout = 0;
> ++ UINT16 FrontPageTimeout;
> ++
> ++ FrontPageTimeout = 0;
> +
> + DEBUG ((DEBUG_INFO, "PlatformBootManagerBeforeConsole\n"));
> + InstallDevicePathCallback ();
> 4: d954947f8d14 ! 4: f3cda3cadde4 OvmfPkg: create a SEV secret area in the AmdSev memfd
> @@ -10,8 +10,9 @@
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> -
> Message-Id: <20201130202819.3910-5-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + [lersek@redhat.com: fix typo in "ResetVectorVtf0.asm" comments]
>
> diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec
> --- a/OvmfPkg/OvmfPkg.dec
> @@ -52,7 +53,7 @@
> +;
> +; SEV Secret block
> +;
> -+; This describes the guest ram area where the hypervisor may should
> ++; This describes the guest ram area where the hypervisor should
> +; inject the secret. The data format is:
> +;
> +; base physical address (32 bit word)
> 5: 1a18c4921cdf ! 5: c38b3caf22ad OvmfPkg/AmdSev: assign and protect the Sev Secret area
> @@ -1,14 +1,17 @@
> Author: James Bottomley <jejb@linux.ibm.com>
>
> - OvmfPkg/AmdSev: assign and protect the Sev Secret area
> + OvmfPkg/AmdSev: assign and reserve the Sev Secret area
>
> - Create a one page secret area in the MEMFD and protect the area with a
> + Create a one page secret area in the MEMFD and reserve the area with a
> boot time HOB.
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Message-Id: <20201130202819.3910-6-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + [lersek@redhat.com: s/protect/reserve/g in the commit message, at Ard's
> + and James's suggestion]
>
> diff --git a/OvmfPkg/AmdSev/AmdSevX64.dsc b/OvmfPkg/AmdSev/AmdSevX64.dsc
> --- a/OvmfPkg/AmdSev/AmdSevX64.dsc
> 6: 6970b9413c93 ! 6: ea823d078162 OvmfPkg/AmdSev: Expose the Sev Secret area using a configuration table
> @@ -11,6 +11,8 @@
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Message-Id: <20201130202819.3910-7-jejb@linux.ibm.com>
> + Acked-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> + [lersek@redhat.com: fix indentation of InstallConfigurationTable() args]
>
> diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec
> --- a/OvmfPkg/OvmfPkg.dec
> @@ -152,7 +154,8 @@
> + IN EFI_SYSTEM_TABLE *SystemTable
> + )
> +{
> -+ return gBS->InstallConfigurationTable (&gSevLaunchSecretGuid,
> -+ &mSecretDxeTable
> -+ );
> ++ return gBS->InstallConfigurationTable (
> ++ &gSevLaunchSecretGuid,
> ++ &mSecretDxeTable
> ++ );
> +}
I meant to include this range-diff in the email where I'd confirm the
merge and the commit range; too bad I got distracted with this ECC mess.
Laszlo
next prev parent reply other threads:[~2020-12-04 2:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 20:28 [PATCH v3 0/6] SEV Encrypted Boot for Ovmf James Bottomley
2020-11-30 20:28 ` [PATCH v3 1/6] OvmfPkg/ResetVector: convert SEV-ES Reset Block structure to be GUIDed James Bottomley
2020-12-03 8:10 ` [edk2-devel] " Laszlo Ersek
2020-11-30 20:28 ` [PATCH v3 2/6] OvmfPkg/Amdsev: Base commit to build encrypted boot specific OVMF James Bottomley
2020-12-03 8:20 ` [edk2-devel] " Laszlo Ersek
2020-11-30 20:28 ` [PATCH v3 3/6] OvmfPkg/AmdSev: add Grub Firmware Volume Package James Bottomley
2020-12-03 8:39 ` [edk2-devel] " Laszlo Ersek
2020-11-30 20:28 ` [PATCH v3 4/6] OvmfPkg: create a SEV secret area in the AmdSev memfd James Bottomley
2020-12-03 8:42 ` [edk2-devel] " Laszlo Ersek
2020-11-30 20:28 ` [PATCH v3 5/6] OvmfPkg/AmdSev: assign and protect the Sev Secret area James Bottomley
2020-12-01 7:54 ` Ard Biesheuvel
2020-12-01 18:36 ` [edk2-devel] " James Bottomley
2020-11-30 20:28 ` [PATCH v3 6/6] OvmfPkg/AmdSev: Expose the Sev Secret area using a configuration table James Bottomley
2020-12-03 8:46 ` [edk2-devel] " Laszlo Ersek
2020-12-09 12:02 ` Yao, Jiewen
2020-12-09 15:46 ` James Bottomley
2020-12-09 15:54 ` James Bottomley
2020-12-09 16:33 ` Yao, Jiewen
2020-12-09 16:38 ` James Bottomley
2020-12-09 16:51 ` Yao, Jiewen
2020-12-09 17:04 ` James Bottomley
2020-12-10 9:12 ` Laszlo Ersek
2020-12-10 9:27 ` Yao, Jiewen
2020-12-01 8:05 ` [PATCH v3 0/6] SEV Encrypted Boot for Ovmf Ard Biesheuvel
2020-12-01 8:13 ` Laszlo Ersek
2020-12-01 15:26 ` James Bottomley
2020-12-01 8:05 ` Laszlo Ersek
2020-12-03 12:26 ` [edk2-devel] " Laszlo Ersek
2020-12-03 14:27 ` James Bottomley
2020-12-04 0:46 ` Laszlo Ersek
2020-12-04 1:05 ` James Bottomley
2020-12-04 1:55 ` Laszlo Ersek
2020-12-04 2:01 ` Laszlo Ersek [this message]
2020-12-14 19:57 ` Laszlo Ersek
2020-12-21 15:00 ` Laszlo Ersek
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=a968365d-e595-7005-16b7-53a0dad22b3d@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