linux-kernel - Re: EFI and multiboot2 devlopment work for Xen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.GSO.2.00.1310211424200.2162@oretfbsg>
Date:	Mon, 21 Oct 2013 14:27:57 -0700 (PDT)
From:	Seth Goldberg <seth.goldberg@...cle.com>
To:	"Vladimir 'φ-coder/phcoder' Serbinenko" 
	<phcoder@...il.com>
cc:	The development of GNU GRUB <grub-devel@....org>, keir@....org,
	david.woodhouse@...el.com, stefano.stabellini@...citrix.com,
	linux-kernel@...r.kernel.org, ross.philipson@...rix.com,
	jbeulich@...e.com, boris.ostrovsky@...cle.com,
	xen-devel@...ts.xen.org, richard.l.maliszewski@...el.com,
	ian.campbell@...rix.com
Subject: Re: EFI and multiboot2 devlopment work for Xen



Quoting Vladimir 'φ-coder/phcoder' Serbinenko, who wrote the following on...:

> On 21.10.2013 22:53, Seth Goldberg wrote:
>>
>>
>> Quoting Daniel Kiper, who wrote the following on Mon, 21 Oct 2013:
>>
>>> 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.
>>
>>   Yes, that is exactly why we added full support to pass the entire UEFI
>> memory map via a new tag.
>>
> Can you send this patch? Or provide a link to publically available
> source? I think we can accept it with probably just minor changes.
>

   Sure :).  Just as an FYI, the changes are available in one of the zips from:

http://www.oracle.com/technetwork/opensource/systems-solaris-1562786.html

   (their size is rather comical of course, but only because they include ALL 
FOSS source shipped with Solaris 11.1).

   I'll try to isolate that change and base it against the current trunk. 
We may need to change the tag id, as I ended up using an OEM-specific number 
for it; I didn't want to conflict with new tags.

  Thanks,
  --S