From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>,
Jian J Wang <jian.j.wang@intel.com>, Hao Wu <hao.a.wu@intel.com>,
Leif Lindholm <leif.lindholm@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: Re: [PATCH v2 0/6] introduce MAX_ALLOC_ADDRESS to limit boot time allocations
Date: Thu, 20 Dec 2018 11:38:32 +0100 [thread overview]
Message-ID: <CAKv+Gu-f8vDjCTxYnLSx8OfrMUKb_5R45M=FFh2bu3p3khbLoA@mail.gmail.com> (raw)
In-Reply-To: <20181219205640.4704-1-ard.biesheuvel@linaro.org>
On Wed, 19 Dec 2018 at 21:56, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> Since modifying MAX_ADDRESS to limit the memory used at boot time has
> turned out to be intractible, this series proposes another approach to do
> the same, by introducing MAX_ALLOC_ADDRESS for firmware internal use.
>
> I tested these patches with ArmVirtQemu in the following way:
> - limit MAX_ALLOC_ADDRESS to 0xFFFFFFFF (4 GB)
> - build QEMU_EFI.fd
> - run it under mach-virt with 4 GB of DRAM and highmem=off
>
> This runs as expected, and produces a memory map ending in the following
> lines
>
> BS_Data 00000000FFFFD000-00000000FFFFFFFF 0000000000000003 0000000000000008
> Available 0000000100000000-000000013FFFFFFF 0000000000040000 0000000000000008
>
> which proves that the memory above the limit is recorded and reported by
> the OS, but left untouched by the firmware memory allocation routines.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao Wu <hao.a.wu@intel.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> 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 (6):
> MdePkg/Base: introduce MAX_ALLOC_ADDRESS
> MdeModulePkg/Dxe/Gcd: disregard memory above MAX_ALLOC_ADDRESS
> MdeModulePkg/Dxe/Page: take MAX_ALLOC_ADDRESS into account
> ArmPkg/ArmMmuLib: take MAX_ALLOC_ADDRESS into account
> ArmPlatformPkg/MemoryInitPeim: take MAX_ALLOC_ADDRESS into account
> ArmVirtPkg/MemoryInitPeiLib: split memory HOB based on
> MAX_ALLOC_ADDRESS
>
Pushed as 5c8bc8be9e5e..4a1500db2b42
Thanks all
prev parent reply other threads:[~2018-12-20 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 20:56 [PATCH v2 0/6] introduce MAX_ALLOC_ADDRESS to limit boot time allocations Ard Biesheuvel
2018-12-19 20:56 ` [PATCH v2 1/6] MdePkg/Base: introduce MAX_ALLOC_ADDRESS Ard Biesheuvel
2018-12-20 6:45 ` Gao, Liming
2018-12-19 20:56 ` [PATCH v2 2/6] MdeModulePkg/Dxe/Gcd: disregard memory above MAX_ALLOC_ADDRESS Ard Biesheuvel
2018-12-19 20:56 ` [PATCH v2 3/6] MdeModulePkg/Dxe/Page: take MAX_ALLOC_ADDRESS into account Ard Biesheuvel
2018-12-20 3:27 ` Wang, Jian J
2018-12-19 20:56 ` [PATCH v2 4/6] ArmPkg/ArmMmuLib: " Ard Biesheuvel
2018-12-19 21:03 ` Leif Lindholm
2018-12-19 20:56 ` [PATCH v2 5/6] ArmPlatformPkg/MemoryInitPeim: " Ard Biesheuvel
2018-12-19 21:15 ` Leif Lindholm
2018-12-19 20:56 ` [PATCH v2 6/6] ArmVirtPkg/MemoryInitPeiLib: split memory HOB based on MAX_ALLOC_ADDRESS Ard Biesheuvel
2018-12-20 10:38 ` 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-f8vDjCTxYnLSx8OfrMUKb_5R45M=FFh2bu3p3khbLoA@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