All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: David Vrabel <dvrabel@cantab.net>
Cc: ian.jackson@eu.citrix.com, Wei Liu <wei.liu2@citrix.com>,
	ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/4] Reintroduce OVMF support
Date: Wed, 16 Oct 2013 14:10:02 +0100	[thread overview]
Message-ID: <20131016131002.GF16371@zion.uk.xensource.com> (raw)
In-Reply-To: <525E8C1B.9060206@cantab.net>

On Wed, Oct 16, 2013 at 01:52:43PM +0100, David Vrabel wrote:
> On 15/10/13 17:40, Wei Liu wrote:
> > This small series reintroduces OVMF support in Xen
> 
> I think somewhere in this series there needs to a brief description of
> what OVMF is.
> 

OVMF is a project to enable UEFI firmware for virtual machines. It's
part of the EDK2 kit. OVMF was first introduced to Xen about a year ago
but it was later disabled due to build process breakage.

Now that the build problem is resolved in upstream we would like to
re-enable it in Xen.

> With the exception of the first patch this is just adding yet another
> component to clone and build.  Why is this useful?  Why isn't
> (effectively) --with-system-ovmf always enabled (and thus not actually
> needed as an option)?
> 

Idealy we should always use the binary provided by distro, but
pratically their binaries are not always up to date / don't always work
with Xen.

> Isn't Xen's keenness to build it's own particular versions of stuff
> something that causes significant problems for distributions?
> 

We've been trying to work closely with upstream to fix bugs. But the
proecess for distros to pick up upstream bug fixes are different
stories which we have no control over.

That's why we provide several --with-system-FOO options in our build
system. The packager can choose in stock binaries if they want to. But
if the in stock binaries don't work they can use our trees.

Wei.

> David

  parent reply	other threads:[~2013-10-16 13:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 16:40 [PATCH 0/4] Reintroduce OVMF support Wei Liu
2013-10-15 16:40 ` [PATCH 1/4] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048 Wei Liu
2013-10-29 12:03   ` George Dunlap
2013-10-29 12:15     ` Wei Liu
2013-10-29 12:24       ` Wei Liu
2013-10-29 12:29         ` George Dunlap
2013-10-29 12:35           ` Wei Liu
2013-10-15 16:40 ` [PATCH 2/4] tools: clone ovmf to ovmf-dir directory Wei Liu
2013-10-16  9:58   ` Jan Beulich
2013-10-16 12:34     ` Wei Liu
2013-10-15 16:40 ` [PATCH 3/4] tools: support system supplied ovmf binary Wei Liu
2013-10-15 16:40 ` [PATCH 4/4] tools: Enable OVMF build by default Wei Liu
2013-10-16 10:02   ` Jan Beulich
2013-10-16 10:37     ` Ian Campbell
2013-10-16 11:38       ` Wei Liu
2013-10-16 12:53         ` Ian Campbell
2013-10-16 13:00           ` Wei Liu
2013-10-16 10:03 ` [PATCH 0/4] Reintroduce OVMF support Fabio Fantoni
2013-10-16 12:51   ` Wei Liu
2013-10-16 14:13     ` Fabio Fantoni
2013-10-16 15:00       ` Wei Liu
2013-10-16 15:17         ` Ian Campbell
2013-10-17  9:13         ` Fabio Fantoni
2013-10-17  9:27           ` Ian Campbell
2013-10-16 12:52 ` David Vrabel
2013-10-16 12:59   ` Ian Campbell
2013-10-16 13:10   ` Wei Liu [this message]
2013-10-28 10:53     ` Fabio Fantoni
2013-10-28 11:32       ` Wei Liu
2013-10-28 12:10 ` Wei Liu

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=20131016131002.GF16371@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=dvrabel@cantab.net \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.