[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52669C2C.90509@gmail.com>
Date: Tue, 22 Oct 2013 17:39:24 +0200
From: Vladimir 'φ-coder/phcoder' Serbinenko
<phcoder@...il.com>
To: The development of GNU GRUB <grub-devel@....org>
CC: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Ian Campbell <ian.campbell@...rix.com>, keir@....org,
david.woodhouse@...el.com, stefano.stabellini@...citrix.com,
Daniel Kiper <daniel.kiper@...cle.com>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xen.org,
Jan Beulich <JBeulich@...e.com>, ross.philipson@...rix.com,
boris.ostrovsky@...cle.com, richard.l.maliszewski@...el.com
Subject: Re: EFI and multiboot2 devlopment work for Xen
On 22.10.2013 16:51, Konrad Rzeszutek Wilk wrote:
> If you use 'linux' module, it will call ExitBootService.
> If you use 'multiboot' module, it will call ExitBootService too.
>
> So if you don't want to the module to call 'grub_efi_finish_boot_services'
> you need to use 'linuxefi' :-)
That's a very limited logic. Commands can be modified and protocols can
be extended.
There was only one e-mail explaining the needs and I answered with
proposing possible solutions yet the 2 e-mails in question were
completely ignored.
What's the need behind not calling ExitBootService? This is a point
which was never really explained to me. EFI specification specifically
tells to call ExitBootService.
Download attachment "signature.asc" of type "application/pgp-signature" (292 bytes)
Powered by blists - more mailing lists