Re: [Xen-devel] [PATCH v11 06/13] efi: create new early memory allocator

2016-12-12 Thread Daniel Kiper
On Fri, Dec 09, 2016 at 06:03:06PM +, Julien Grall wrote: > Hi Daniel, > > On 05/12/16 22:25, Daniel Kiper wrote: > >There is a problem with place_string() which is used as early memory > >allocator. It gets memory chunks starting from start symbol and goes > >down. Sadly this does not work whe

Re: [Xen-devel] [PATCH v11 06/13] efi: create new early memory allocator

2016-12-09 Thread Julien Grall
Hi Daniel, On 05/12/16 22:25, Daniel Kiper wrote: There is a problem with place_string() which is used as early memory allocator. It gets memory chunks starting from start symbol and goes down. Sadly this does not work when Xen is loaded using multiboot2 protocol because then the start lives on

Re: [Xen-devel] [PATCH v11 06/13] efi: create new early memory allocator

2016-12-06 Thread Jan Beulich
>>> On 05.12.16 at 23:25, wrote: > There is a problem with place_string() which is used as early memory > allocator. It gets memory chunks starting from start symbol and goes > down. Sadly this does not work when Xen is loaded using multiboot2 > protocol because then the start lives on 1 MiB addre

[Xen-devel] [PATCH v11 06/13] efi: create new early memory allocator

2016-12-05 Thread Daniel Kiper
There is a problem with place_string() which is used as early memory allocator. It gets memory chunks starting from start symbol and goes down. Sadly this does not work when Xen is loaded using multiboot2 protocol because then the start lives on 1 MiB address and we should not allocate a memory fro