From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Fri, 15 Jan 2016 04:40:55 +0100 Subject: [U-Boot] [PATCH 4/9] efi_loader: Add boot time services In-Reply-To: <20151226180901.GY25034@bivouac.eciton.net> References: <1450792676-109541-1-git-send-email-agraf@suse.de> <1450792676-109541-5-git-send-email-agraf@suse.de> <20151226180901.GY25034@bivouac.eciton.net> Message-ID: <56986A47.4050500@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 26.12.15 19:09, Leif Lindholm wrote: > On Tue, Dec 22, 2015 at 02:57:51PM +0100, Alexander Graf wrote: [...] >> + break; >> + case 2: >> + /* Exact address, grant it. The addr is already in *memory. */ > > As far as I can tell, this is why GRUB works. Because it filters > through the memory map manually, requesting to allocate its heap at an > exact address in a region of free memory in the UEFI memory map. > > The key is that EFI_LOADER_MEMORY will be used by applications loaded > as well as by U-Boot to load applications into. A simple example where > this could be problematic would be a large(ish) initrd loaded via initrd= > on kernel (stub loader) command line rather than via GRUB. Thinking about this once more, we don't expose any file system interfaces to EFI applications, so initrd= won't work anyway. That means the only viable path to go right now is via grub which means we shouldn't get into memory contention with 128MB LOADER_DATA. Alex