lkml.org 
[lkml]   [2014]   [Mar]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v3 3/5] x86: Call efi_memblock_x86_reserve_range() on native EFI platform only
    >>> On 26.03.14 at 14:31, <matt@console-pimps.org> wrote:
    > On Wed, 26 Mar, at 01:22:49PM, Jan Beulich wrote:
    >> >>> On 26.03.14 at 14:00, <matt@console-pimps.org> wrote:
    >> >
    >> > This could do with a little bit more explanation. Why is it not
    >> > necessary to mark the EFI memory map that was passed to the kernel as
    >> > reserved in memblock?
    >>
    >> Because that's in memory Dom0 doesn't even see: The EFI memory
    >> map is visible to the hypervisor only.
    >
    > So where does boot_params.efi_info.efi_memmap point?
    >
    > If nowhere (i.e. it's NULL) that's no problem because memblock_reserve()
    > handles zero size regions just fine.

    That's a question to Daniel - in our implementation (with a separate
    Xen kernel that can't run on bare hardware) boot_params as a whole
    simply doesn't exist.

    Jan



    \
     
     \ /
      Last update: 2014-03-26 15:21    [W:8.262 / U:0.076 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site