[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 12/16 - RFC] x86/efi: create new early memory allocator
>>> On 02.06.16 at 12:43, <daniel.kiper@xxxxxxxxxx> wrote: > I have checked the code once again. On ARM we allocate memory using > EfiLoaderData (not only for memory map) and later deliberately do not > take over these regions. This means that memory map persists. However, > this also means that we are not able to use a lot of memory which is > free from Xen point of view (for more details please check Unified > Extensible Firmware Interface Specification, Version 2.6, section 6.2, > Memory Allocation Services). Why? AFAICT, EfiLoaderCode/EfiLoaderData > types are used very often by EFI applications to allocate memory > dynamically. Most of these applications are dead after ExitBootServices(). > So, there is pretty good chance that we are loosing quite big chunk > of memory which simply contains junk except of small portion with memory > map. And on ARM, especially on embedded, this could be painful. > > On x86 we take over EfiLoaderCode/EfiLoaderData regions. And I do not > think we should change that behavior. Even maybe we should change > behavior on ARM. Hmmm... Is it possible? Was there a reason to not > take over EfiLoaderCode/EfiLoaderData regions on ARM? That's not a question to me, I suppose (despite me being the only one on the To list)? Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |