[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52663D54.2020800@gmail.com>
Date: Tue, 22 Oct 2013 10:54:44 +0200
From: Vladimir 'φ-coder/phcoder' Serbinenko
<phcoder@...il.com>
To: The development of GNU GRUB <grub-devel@....org>
CC: Daniel Kiper <daniel.kiper@...cle.com>, boris.ostrovsky@...cle.com,
david.woodhouse@...el.com, ian.campbell@...rix.com,
jbeulich@...e.com, keir@....org, konrad.wilk@...cle.com,
pjones@...hat.com, richard.l.maliszewski@...el.com,
ross.philipson@...rix.com, stefano.stabellini@...citrix.com,
xen-devel@...ts.xen.org, linux-kernel@...r.kernel.org
Subject: Re: EFI and multiboot2 devlopment work for Xen
On 21.10.2013 23:16, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Mail is big, I think I got your essential points but I didn't read it whole.
> On 21.10.2013 14:57, Daniel Kiper wrote:
>> Hi,
>>
>> During work on multiboot2 protocol support for Xen it was discovered
>> that memory map passed via relevant tag could not represent wide range
>> of memory types available on EFI platforms. Additionally, GRUB2
>> implementation calls ExitBootServices() on them just before jumping
>> into loaded image. In this situation loaded system could not clearly
>> identify reserved memory regions, EFI runtime services regions and others.
>>
> Will a multiboot2 tag with whole EFI memory map solve your problem?
I added such a tag in documentation and wrote a patch for it (attached).
Awaiting for someone to test it to commit
Download attachment "efi.diff" of type "application/x-patch" (4747 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (292 bytes)
Powered by blists - more mailing lists