summaryrefslogtreecommitdiffstats
path: root/NetworkPkg
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2020-05-08 14:16:51 +0200
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2020-05-18 15:48:48 +0000
commit7b6327ff03bb4436261ffad246ba3a14de10391f (patch)
treee8389dc7299a9f970a9e1c9483e12e7f96e3ad92 /NetworkPkg
parent8db87f98357b40798a9446d96d9b9109c9cbb47e (diff)
downloadedk2-7b6327ff03bb4436261ffad246ba3a14de10391f.tar.gz
edk2-7b6327ff03bb4436261ffad246ba3a14de10391f.tar.bz2
edk2-7b6327ff03bb4436261ffad246ba3a14de10391f.zip
OvmfPkg/PlatformPei: increase memory type info defaults
Any new OVMF binary (containing commit d42fdd6f8384, and built with SMM_REQUIRE) is likely to reboot during its first boot, regardless of whether the variable store is logically empty, or it contains a MemoryTypeInformation variable from an earlier OVMF binary. This "reboot on first boot after OVMF upgrade" occurs despite having eliminated BS Code/Data tracking in earlier parts of this series. Meaning that we've outgrown the bins of those memory types too that matter for SMM security. Eliminating said reboot will make an upgrade to edk2-stable202005 more comfortable for users. Increase the defaults empirically. (The total doesn't exceed 3MB by much.) Cc: Ard Biesheuvel <ard.biesheuvel@arm.com> Cc: Jiewen Yao <jiewen.yao@intel.com> Cc: Jordan Justen <jordan.l.justen@intel.com> Cc: Philippe Mathieu-Daudé <philmd@redhat.com> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2706 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Message-Id: <20200508121651.16045-5-lersek@redhat.com> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
Diffstat (limited to 'NetworkPkg')
0 files changed, 0 insertions, 0 deletions