All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: ian.jackson@eu.citrix.com, wei.liu2@citrix.com,
	ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] add upstream GRUB to the Xen build system
Date: Fri, 13 Mar 2015 16:24:11 +0000	[thread overview]
Message-ID: <55030F2B.5090208@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503131559060.7982@kaball.uk.xensource.com>

On 13/03/15 16:02, Stefano Stabellini wrote:
> On Fri, 13 Mar 2015, David Vrabel wrote:
>> On 13/03/15 15:33, Stefano Stabellini wrote:
>>> Clone and build upstream GRUB to generate x86_64 and i386 pvgrub2
>>> binaries. See Ian's blog post for more information:
>>
>> Why?  If pvgrub2 is available on the system libxl should make use of it,
>> but there doesn't seem to be a good reason for cloning and building yet
>> another third-party project as part of the Xen build.
>>
>> At a minimum this needs a configure option to disable it.
> 
> It is the only way to boot grub2 pv guests securely.  More importantly
> it is also the first step toward adding an osstest test for upstream
> grub.

osstest can clone and build grub if necessary, it doesn't need to be
part of the Xen build.

> Finally it will allow us to get rid of pvgrub1 in the future. As a
> matter of fact I already have a patch to remove pvgrub, if the
> maintainers feel that it is already the time I am happy to send it out.

The majority of projects would handle this by listing grub 2.x as a
requirement in the release notes or similar.

David

  reply	other threads:[~2015-03-13 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 15:33 [PATCH] add upstream GRUB to the Xen build system Stefano Stabellini
2015-03-13 15:55 ` Stefano Stabellini
2015-03-13 15:58 ` David Vrabel
2015-03-13 16:02   ` Stefano Stabellini
2015-03-13 16:24     ` David Vrabel [this message]
2015-03-16 12:22       ` Fabio Fantoni

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=55030F2B.5090208@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@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.