linux-kernel - Re: [Xen-devel] 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]

Date:	Thu, 24 Oct 2013 07:53:57 +0100
From:	"Jan Beulich" <jbeulich@...e.com>
To:	<phcoder@...il.com>, <grub-devel@....org>
Cc:	<ian.campbell@...rix.com>, <ross.philipson@...rix.com>,
	<stefano.stabellini@...citrix.com>, <david.woodhouse@...el.com>,
	<richard.l.maliszewski@...el.com>, <xen-devel@...ts.xen.org>,
	<boris.ostrovsky@...cle.com>, <daniel.kiper@...cle.com>,
	<konrad.wilk@...cle.com>, <mjg59@...f.ucam.org>,
	<linux-kernel@...r.kernel.org>, <keir@....org>
Subject: Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen

>>> Vladimir 'φ-coder/phcoder' Serbinenko<phcoder@...il.com> 10/23/13 7:02 PM >>>
>> GrUB - which iiuc stays in memory
>> after transferring control - could export its file system support to its
>> descendants).
>
>Xen shouldn't need to load any file after multiboot2 entry point. The
>needed files would already be in memory with pointers to them passed.

I should have said "to its chainloaded descendants".

>If you insist on being able to load directly from EFI, then IMO the best
>way is to have a PE executable with one of sections containing Xen and
>code which would load remaining files to memory and call common entry point.

I think you've been told before - this is what has been working already for quite
some time.

Jan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/