From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Laszlo Ersek <lersek@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Philippe Mathieu-Daude <philmd@redhat.com>
Subject: [PATCH v2 0/2] ArmVirtPkg: remove high peripheral space mapping
Date: Tue, 27 Nov 2018 15:54:16 +0100 [thread overview]
Message-ID: <20181127145418.11992-1-ard.biesheuvel@linaro.org> (raw)
Stop mapping the entire address space in the early PEI code. This
wastes temporary RAM on page tables, and encourages sloppy coding
when it comes to populating the GCD memory map.
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>
Cc: Philippe Mathieu-Daude <philmd@redhat.com>
Ard Biesheuvel (2):
ArmVirtPkg/FdtPciHostBridgeLib: map ECAM and I/O spaces in GCD memory
map
ArmVirtPkg/QemuVirtMemInfoLib: remove 1:1 mapping of top of PA range
.../FdtPciHostBridgeLib.inf | 1 +
.../FdtPciHostBridgeLib/FdtPciHostBridgeLib.c | 46 ++++++++++++++++++-
.../QemuVirtMemInfoLib/QemuVirtMemInfoLib.c | 17 ++-----
3 files changed, 51 insertions(+), 13 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-27 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:54 Ard Biesheuvel [this message]
2018-11-27 14:54 ` [PATCH v2 1/2] ArmVirtPkg/FdtPciHostBridgeLib: map ECAM and I/O spaces in GCD memory map Ard Biesheuvel
2018-11-27 15:28 ` Philippe Mathieu-Daudé
2018-11-27 17:40 ` Laszlo Ersek
2018-11-27 17:47 ` Ard Biesheuvel
2018-11-27 14:54 ` [PATCH v2 2/2] ArmVirtPkg/QemuVirtMemInfoLib: remove 1:1 mapping of top of PA range Ard Biesheuvel
2018-11-27 17:26 ` Laszlo Ersek
2018-11-27 17:52 ` Ard Biesheuvel
2018-11-27 20:25 ` Laszlo Ersek
2018-11-27 21:18 ` Ard Biesheuvel
2018-11-28 12:12 ` 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=20181127145418.11992-1-ard.biesheuvel@linaro.org \
--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