From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: [PATCH] Replace bios_relocate hook with bios_load hook in hvmloader Date: Wed, 27 Jul 2011 09:35:22 +0100 Message-ID: References: <20110727080920.GO8970@whitby.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110727080920.GO8970@whitby.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tim Deegan Cc: Xen Devel , Jordan Justen , Bei Guan , Andrei Warkentin List-Id: xen-devel@lists.xenproject.org On 27/07/2011 09:09, "Tim Deegan" wrote: > At 08:34 +0100 on 27 Jul (1311755670), Keir Fraser wrote: >> By the way, what are the advantages for us of supporting OVMF? I know it >> gets us the UEFI support tickybox, but for me that begs the same question. >> Why is it useful? > > When Windows boots from UEFI it can load just its system-disk driver via > the firmware and the rest of the OS using its own driver; that ought to > make Windows boot times much faster. That's interesting. Why can't it do that with legacy firmware? Does it need to keep the legacy BIOS alive for a while and hence can't use its own drivers, or something like that? -- Keir > I'm told that an EFI framebuffer > could make PV graphics easier too, but I don't know anything about > Windows graphics drivers. > > Also, eventually some server SKUs may go EFI-only, or we may need EFI > for system logo tests, but that seems unlikely to happen soon. > > Tim.