All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <Tim.Deegan@citrix.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
	Jordan Justen <jljusten@gmail.com>, Bei Guan <gbtju85@gmail.com>,
	Andrei Warkentin <andreiw@motorola.com>
Subject: Re: Re: [PATCH] Replace bios_relocate hook with bios_load hook in hvmloader
Date: Wed, 27 Jul 2011 09:09:20 +0100	[thread overview]
Message-ID: <20110727080920.GO8970@whitby.uk.xensource.com> (raw)
In-Reply-To: <CA557E16.1EA17%keir.xen@gmail.com>

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.  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.

-- 
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

  reply	other threads:[~2011-07-27  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 19:02 [PATCH] Replace bios_relocate hook with bios_load hook in hvmloader Bei Guan
2011-07-25 13:23 ` Keir Fraser
2011-07-26 13:29   ` Andrei Warkentin
2011-07-27  7:34     ` Keir Fraser
2011-07-27  8:09       ` Tim Deegan [this message]
2011-07-27  8:35         ` Keir Fraser
2011-07-27  8:45           ` Tim Deegan
2011-07-27 17:55           ` Andrei Warkentin
2011-07-27  2:02   ` Bei Guan
2011-07-27  7:10     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110727080920.GO8970@whitby.uk.xensource.com \
    --to=tim.deegan@citrix.com \
    --cc=andreiw@motorola.com \
    --cc=gbtju85@gmail.com \
    --cc=jljusten@gmail.com \
    --cc=keir.xen@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.