From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Gary Ching-Pang Lin <glin@suse.com>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: [PATCH v2 0/5] OvmfPkg: add FD_SIZE_4MB for Windows HCK SB tests, and for future proofing
Date: Wed, 3 May 2017 23:39:42 +0200 [thread overview]
Message-ID: <20170503213947.32290-1-lersek@redhat.com> (raw)
This is version 2 of the series posted at
<https://lists.01.org/pipermail/edk2-devel/2017-April/010334.html>.
Changes in v2:
- consolidate FD_SIZE_1MB, FD_SIZE_2MB, FD_SIZE_4MB, basing them all on
the new macro FD_SIZE_IN_KB,
- increase the variable store from 248 KB to 256 KB, and propagate that
change as necessary, at the expense of FVMAIN_COMPACT [Jordan],
- make the 4MB build the general default [Jordan].
V1->v2 changes are also marked on the individual patches.
Thoroughly retested with the usual S3 stuff, the Secure Boot Logo Test,
multiple purposefully triggered reclaims, hexdumps of varstore files,
etc.
Formatted with 13 lines of context for easier review.
Repo: https://github.com/lersek/edk2.git
Branch: fd_size_4mb_v2
Cc: Gary Ching-Pang Lin <glin@suse.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Thanks,
Laszlo
Laszlo Ersek (5):
OvmfPkg: introduce the FD_SIZE_IN_KB macro / build flag
OvmfPkg/OvmfPkg.fdf.inc: extract VARS_LIVE_SIZE and VARS_SPARE_SIZE
macros
OvmfPkg: introduce 4MB flash image (mainly) for Windows HCK
OvmfPkg: raise max variable size (auth & non-auth) to 33KB for
FD_SIZE_4MB
OvmfPkg: make the 4MB flash size the default
OvmfPkg/OvmfPkgIa32.dsc | 25 +++++++++
OvmfPkg/OvmfPkgIa32X64.dsc | 25 +++++++++
OvmfPkg/OvmfPkgX64.dsc | 25 +++++++++
OvmfPkg/OvmfPkg.fdf.inc | 46 ++++++++++++-----
OvmfPkg/VarStore.fdf.inc | 54 +++++++++++++++++++-
5 files changed, 161 insertions(+), 14 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-03 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 21:39 Laszlo Ersek [this message]
2017-05-03 21:39 ` [PATCH v2 1/5] OvmfPkg: introduce the FD_SIZE_IN_KB macro / build flag Laszlo Ersek
2017-05-03 21:39 ` [PATCH v2 2/5] OvmfPkg/OvmfPkg.fdf.inc: extract VARS_LIVE_SIZE and VARS_SPARE_SIZE macros Laszlo Ersek
2017-05-03 21:39 ` [PATCH v2 3/5] OvmfPkg: introduce 4MB flash image (mainly) for Windows HCK Laszlo Ersek
2017-05-05 4:07 ` Laszlo Ersek
2017-05-05 8:57 ` Jordan Justen
2017-05-05 12:07 ` Laszlo Ersek
2017-05-05 15:43 ` Jordan Justen
2017-05-05 16:46 ` Laszlo Ersek
2017-05-03 21:39 ` [PATCH v2 4/5] OvmfPkg: raise max variable size (auth & non-auth) to 33KB for FD_SIZE_4MB Laszlo Ersek
2017-05-04 16:36 ` Jordan Justen
2017-05-04 16:52 ` Laszlo Ersek
2017-05-04 18:50 ` Jordan Justen
2017-05-04 19:27 ` Laszlo Ersek
2017-05-04 19:30 ` Laszlo Ersek
2017-05-04 23:00 ` Laszlo Ersek
2017-05-03 21:39 ` [PATCH v2 5/5] OvmfPkg: make the 4MB flash size the default 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=20170503213947.32290-1-lersek@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