From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>,
Jian J Wang <jian.j.wang@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Zhang, Chao B" <chao.b.zhang@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 0/3] remove most occurrences of ELILO on IPF PE/COFF header hack
Date: Mon, 24 Sep 2018 16:58:08 +0200 [thread overview]
Message-ID: <CAKv+Gu-c-D9GdByd4Cv3zxnReHB-h-RZYOH=vah9fZaKAfeYhA@mail.gmail.com> (raw)
In-Reply-To: <20180907054202.24798-1-ard.biesheuvel@linaro.org>
On Fri, 7 Sep 2018 at 07:42, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> Now that Itanium support has been dropped from EDK2, we can remove most
> occurrences of the ELILO PE/COFF loader hack from the code base.
>
> Note that SecurityPkg appears to have four mostly identical implementations
> of the PE/COFF measuring routine, so this may be another area for cleanup
> later.
>
> Changes since v1:
> - fix copy/paste error in patch #3 which went unnoticed due to the fact that
> SecurityPkg.dsc does not cover the module in question for AARCH64
> - drop EdkCompatibilityPkg patch, it is likely to go away soon anyway
> - add Reviewed-by tags
>
> Link: https://bugzilla.tianocore.org/show_bug.cgi?id=816
>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
>
> Ard Biesheuvel (3):
> MdeModulePkg: remove PE/COFF header workaround for ELILO on IPF
> MdePkg/BasePeCoffLib: remove PE/COFF header workaround for ELILO on
> IPF
> SecurityPkg: remove PE/COFF header workaround for ELILO on IPF
>
Patches 1-2 pushed as 997731e796f5..60eb6c6d2e01 (#3 was merged
independently by Chao)
Thanks all
> .../Core/Dxe/Mem/MemoryProfileRecord.c | 31 +---------
> MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c | 17 +-----
> MdeModulePkg/Core/Dxe/Misc/PropertiesTable.c | 17 +-----
> .../Core/PiSmmCore/MemoryAttributesTable.c | 17 +-----
> .../Core/PiSmmCore/SmramProfileRecord.c | 31 +---------
> MdePkg/Library/BasePeCoffLib/BasePeCoff.c | 61 +++----------------
> .../DxeImageVerificationLib.c | 47 +++-----------
> .../DxeTpmMeasureBootLib.c | 27 ++------
> SecurityPkg/Tcg/Tcg2Dxe/MeasureBootPeCoff.c | 27 ++------
> .../SecureBootConfigImpl.c | 25 ++------
> 10 files changed, 39 insertions(+), 261 deletions(-)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2018-09-24 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 5:41 [PATCH v2 0/3] remove most occurrences of ELILO on IPF PE/COFF header hack Ard Biesheuvel
2018-09-07 5:42 ` [PATCH v2 1/3] MdeModulePkg: remove PE/COFF header workaround for ELILO on IPF Ard Biesheuvel
2018-09-07 5:42 ` [PATCH v2 2/3] MdePkg/BasePeCoffLib: " Ard Biesheuvel
2018-09-07 5:42 ` [PATCH v2 3/3] SecurityPkg: " Ard Biesheuvel
2018-09-07 8:28 ` Laszlo Ersek
2018-09-19 21:47 ` Ard Biesheuvel
2018-09-20 5:08 ` Yao, Jiewen
2018-09-20 13:54 ` Zhang, Chao B
2018-09-24 14:58 ` Ard Biesheuvel [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='CAKv+Gu-c-D9GdByd4Cv3zxnReHB-h-RZYOH=vah9fZaKAfeYhA@mail.gmail.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