From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io
Cc: Pawel Polawski <ppolawsk@redhat.com>,
Guomin Jiang <guomin.jiang@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Xiaoyu Lu <xiaoyu1.lu@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Min Xu <min.m.xu@intel.com>, Jian J Wang <jian.j.wang@intel.com>,
Michael Roth <michael.roth@amd.com>,
Oliver Steffen <osteffen@redhat.com>,
James Bottomley <jejb@linux.ibm.com>,
Erdem Aktas <erdemaktas@google.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: [PATCH v2 00/10] OvmfPkg: add Crypto Driver support
Date: Thu, 9 Feb 2023 11:26:38 +0100 [thread overview]
Message-ID: <20230209102648.2291743-1-kraxel@redhat.com> (raw)
Known problem: the NOOPT builds fail due to PEI becoming too big.
What is the reason for doing these NOOPT builds? I'm not sure what
value they provide. But the lack of LTO bloats the binaries with dead
code, which is a constant source of trouble ...
v2 changes:
- turn on crypto driver support by default.
- left the config option in for now as fallback option.
When all goes as planned remove it one or two releases
later.
- fix various build problems.
Gerd Hoffmann (10):
CryptoPkg: move Driver PCD configs to include files
CryptoPkg: add CryptoServicePcd.hash_only.dsc.inc
CryptoPkg: add TPM hashes to CryptoServicePcd.min_dxe_smm.dsc.inc
OvmfPkg: add OvmfCrypto*.inc
OvmfPkg: OvmfPkgX64: use crypto includes
OvmfPkg: OvmfPkgIa32X64: use crypto includes
OvmfPkg: OvmfPkgIa32: use crypto includes
OvmfPkg: Microvm: use crypto includes
OvmfPkg: IntelTdx: use crypto includes
OvmfPkg: AmdSev: use crypto includes
.../Include/Dsc/CryptoServicePcd.all.dsc.inc | 29 +++++++
.../Dsc/CryptoServicePcd.hash_only.dsc.inc | 8 ++
.../Dsc/CryptoServicePcd.min_dxe_smm.dsc.inc | 37 +++++++++
.../Dsc/CryptoServicePcd.min_pei.dsc.inc | 20 +++++
.../Dsc/OvmfCryptoComponentsDxe.dsc.inc | 23 ++++++
.../Dsc/OvmfCryptoComponentsPei.dsc.inc | 19 +++++
.../Dsc/OvmfCryptoComponentsSmm.dsc.inc | 18 +++++
OvmfPkg/Include/Dsc/OvmfCryptoDefines.dsc.inc | 5 ++
OvmfPkg/Include/Dsc/OvmfCryptoLibs.dsc.inc | 57 ++++++++++++++
CryptoPkg/CryptoPkg.dsc | 78 +------------------
OvmfPkg/AmdSev/AmdSevX64.dsc | 12 ++-
OvmfPkg/IntelTdx/IntelTdxX64.dsc | 15 ++--
OvmfPkg/Microvm/MicrovmX64.dsc | 24 +++---
OvmfPkg/OvmfPkgIa32.dsc | 22 +++---
OvmfPkg/OvmfPkgIa32X64.dsc | 22 +++---
OvmfPkg/OvmfPkgX64.dsc | 22 +++---
OvmfPkg/AmdSev/AmdSevX64.fdf | 6 ++
OvmfPkg/IntelTdx/IntelTdxX64.fdf | 5 ++
OvmfPkg/Microvm/MicrovmX64.fdf | 7 ++
OvmfPkg/OvmfPkgIa32.fdf | 6 ++
OvmfPkg/OvmfPkgIa32X64.fdf | 6 ++
OvmfPkg/OvmfPkgX64.fdf | 6 ++
OvmfPkg/Include/Fdf/OvmfCryptoDxeSmm.fdf.inc | 12 +++
OvmfPkg/Include/Fdf/OvmfCryptoPei.fdf.inc | 9 +++
24 files changed, 331 insertions(+), 137 deletions(-)
create mode 100644 CryptoPkg/Include/Dsc/CryptoServicePcd.all.dsc.inc
create mode 100644 CryptoPkg/Include/Dsc/CryptoServicePcd.hash_only.dsc.inc
create mode 100644 CryptoPkg/Include/Dsc/CryptoServicePcd.min_dxe_smm.dsc.inc
create mode 100644 CryptoPkg/Include/Dsc/CryptoServicePcd.min_pei.dsc.inc
create mode 100644 OvmfPkg/Include/Dsc/OvmfCryptoComponentsDxe.dsc.inc
create mode 100644 OvmfPkg/Include/Dsc/OvmfCryptoComponentsPei.dsc.inc
create mode 100644 OvmfPkg/Include/Dsc/OvmfCryptoComponentsSmm.dsc.inc
create mode 100644 OvmfPkg/Include/Dsc/OvmfCryptoDefines.dsc.inc
create mode 100644 OvmfPkg/Include/Dsc/OvmfCryptoLibs.dsc.inc
create mode 100644 OvmfPkg/Include/Fdf/OvmfCryptoDxeSmm.fdf.inc
create mode 100644 OvmfPkg/Include/Fdf/OvmfCryptoPei.fdf.inc
--
2.39.1
next reply other threads:[~2023-02-09 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:26 Gerd Hoffmann [this message]
2023-02-09 10:26 ` [PATCH v2 01/10] CryptoPkg: move Driver PCD configs to include files Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 02/10] CryptoPkg: add CryptoServicePcd.hash_only.dsc.inc Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 03/10] CryptoPkg: add TPM hashes to CryptoServicePcd.min_dxe_smm.dsc.inc Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 04/10] OvmfPkg: add OvmfCrypto*.inc Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 05/10] OvmfPkg: OvmfPkgX64: use crypto includes Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 06/10] OvmfPkg: OvmfPkgIa32X64: " Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 07/10] OvmfPkg: OvmfPkgIa32: " Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 08/10] OvmfPkg: Microvm: " Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 09/10] OvmfPkg: IntelTdx: " Gerd Hoffmann
2023-02-09 10:26 ` [PATCH v2 10/10] OvmfPkg: AmdSev: " Gerd Hoffmann
2023-02-09 16:46 ` [PATCH v2 00/10] OvmfPkg: add Crypto Driver support Ard Biesheuvel
2023-02-10 8:41 ` Gerd Hoffmann
2023-02-10 13:42 ` Ard Biesheuvel
2023-02-10 13:46 ` Ard Biesheuvel
2023-02-13 11:39 ` Gerd Hoffmann
2023-02-13 11:45 ` [edk2-devel] " Ard Biesheuvel
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=20230209102648.2291743-1-kraxel@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