Re: [PATCH V2] efi_high_alloc: use EFI_ALLOCATE_MAX_ADDRESS

2014-08-27 Thread Matt Fleming
On Mon, 25 Aug, at 04:33:54PM, Harald Hoyer wrote: > > So is that ok, if other callers of efi_high_alloc() get an address > > 4GB? Yeah, the issue at hand is that some x86 EFI firmware cannot perform a file read into a buffer above 4G. The actual allocation works fine. If other callers want a hi

Re: [PATCH V2] efi_high_alloc: use EFI_ALLOCATE_MAX_ADDRESS

2014-08-25 Thread Harald Hoyer
On 25.08.2014 15:07, Matt Fleming wrote: > On Mon, 25 Aug, at 01:55:32PM, har...@redhat.com wrote: >> From: Harald Hoyer >> >> On my Lenovo T420s with 4GB memory, efi_high_alloc() was checking the >> following memory regions: >> >> 0x0010 - 0x2000 >> 0x2020 - 0x

Re: [PATCH V2] efi_high_alloc: use EFI_ALLOCATE_MAX_ADDRESS

2014-08-25 Thread Matt Fleming
On Mon, 25 Aug, at 01:55:32PM, har...@redhat.com wrote: > From: Harald Hoyer > > On my Lenovo T420s with 4GB memory, efi_high_alloc() was checking the > following memory regions: > > 0x0010 - 0x2000 > 0x2020 - 0x4000 > 0x4020 - 0x00

[PATCH V2] efi_high_alloc: use EFI_ALLOCATE_MAX_ADDRESS

2014-08-25 Thread harald
From: Harald Hoyer On my Lenovo T420s with 4GB memory, efi_high_alloc() was checking the following memory regions: 0x0010 - 0x2000 0x2020 - 0x4000 0x4020 - 0xd2c02000 0xd6e9f000 - 0x00011e60 and decided to alloc