From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: George Dunlap <george.dunlap@citrix.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"Matt Fleming" <matt@codeblueprint.co.uk>,
jeffm@suse.com, "Michael Chang" <MChang@suse.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jim Fehlig" <jfehlig@suse.com>,
"Jan Beulich" <JBeulich@suse.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Daniel Kiper" <daniel.kiper@oracle.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Takashi Iwai" <tiwai@suse.de>,
"Vojtěch Pavlík" <vojtech@suse.cz>, "Gary Lin" <GLin@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Jeffrey Cheung" <JCheung@suse.com>,
"Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
joeyli <jlee@suse.com>, "Borislav Petkov" <bp@alien8.de>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Charles Arndol" <carnold@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Julien Grall" <julien.grall@arm.com>,
"Andy Lutomirski" <luto@amacapital.net>,
"David Vrabel" <david.vrabel@citrix.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] HVMLite / PVHv2 - using x86 EFI boot entry
Date: Thu, 14 Apr 2016 21:44:08 +0200 [thread overview]
Message-ID: <20160414194408.GP1990@wotan.suse.de> (raw)
In-Reply-To: <570F68AB.2040400@citrix.com>
On Thu, Apr 14, 2016 at 10:53:47AM +0100, George Dunlap wrote:
> On 13/04/16 20:52, Luis R. Rodriguez wrote:
> > On Wed, Apr 13, 2016 at 04:44:54PM +0100, George Dunlap wrote:
> >> On Thu, Apr 7, 2016 at 7:51 PM, Luis R. Rodriguez <mcgrof@suse.com> wrote:
> >>> So more to it, if the EFI entry already provides a way into Linux
> >>> in a more streamlined fashion bringing it closer to the bare metal
> >>> boot entry, why *would* we add another boot entry to x86, even if
> >>> its small and self contained ?
> >>
> >> We would avoid using EFI if:
> >
> > And this is what I was looking for, thanks!
> >
> >> * Being called both on real hardware and under Xen would make the EFI
> >> entry point more complicated
> >
> > That's on the EFI Linux maintainer to assess. And he seems willing to
> > consider this.
> >
> >> * Adding the necessary EFI support into Xen would be a significant
> >> chunk of extra work
> >
> > This seems to be a good sticking point, but Andi noted another aspect
> > of this or redundancy as well.
> >
> >> * Requiring PVH mode to implement EFI would make it more difficult for
> >> other kernes (NetBSD, FreeBSD) to act as dom0s.
> >
> > What if this is an option only then ?
> >
> >>
> >> * Requiring PVH mode to use EFI would make it more difficult to
> >> support unikernel-style workloads for domUs.
> >
> > What if this is an option only then ?
>
> So first of all, you asked why anyone would oppose EFI, and this is part
> of the answer to that.
>
> Secondly, you mean "What if this is the only thing the Linux maintainers
> will accept?" And you already know the answer to that.
No, I meant to ask, would it be possible to make booting HVMLite using EFI
be optional ? That way if you already support EFI that can be used on
your entires with some small modifications.
> How much of a burden it would be on the rest of the open-source
> ecosystem (Xen, *BSDs, &c) is a combination of some as-yet unknown facts
> (i.e., what a minimal Xen/Linux EFI interface would look like) and a
> matter of judgement (i.e., given the same interface, reasonable people
> may come to different conclusions about whether the interface is an
> undue burden to impose on others or not).
>
> But I would hope that the Linux maintainers would at least consider the
> broader community when weighing their decisions, and not take advantage
> of their position of dominance to simply ignore the effect of their
> choices on everybody else.
This has nothing to do with dominance or anything nefarious, I'm asking
simply for a full engineering evaluation of all possibilities, with
the long term in mind. Not for now, but for hardware assumptions which
are sensible 5 years from now.
Luis
next prev parent reply other threads:[~2016-04-14 19:44 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 2:40 HVMLite / PVHv2 - using x86 EFI boot entry Luis R. Rodriguez
2016-04-06 9:40 ` David Vrabel
2016-04-08 20:40 ` Luis R. Rodriguez
2016-04-11 5:12 ` Juergen Gross
2016-04-12 21:02 ` Andy Lutomirski
2016-04-13 9:02 ` Roger Pau Monné
2016-04-13 10:15 ` Matt Fleming
2016-04-13 10:40 ` Matt Fleming
2016-04-13 11:12 ` [Xen-devel] " George Dunlap
2016-04-13 11:59 ` Roger Pau Monné
2016-04-15 22:53 ` Matt Fleming
2016-04-13 18:29 ` Luis R. Rodriguez
[not found] ` <20160413185629.GA7501@char.us.oracle.com>
2016-04-13 20:40 ` [Xen-devel] " Luis R. Rodriguez
[not found] ` <20160413210801.GC5962@char.us.oracle.com>
2016-04-13 22:23 ` Luis R. Rodriguez
2016-04-14 1:01 ` Konrad Rzeszutek Wilk
2016-04-14 18:40 ` Luis R. Rodriguez
2016-04-14 19:56 ` Konrad Rzeszutek Wilk
2016-04-14 20:56 ` Luis R. Rodriguez
2016-04-15 2:02 ` Konrad Rzeszutek Wilk
2016-04-15 17:08 ` Luis R. Rodriguez
2016-04-15 10:06 ` Julien Grall
2016-04-15 14:55 ` Luis R. Rodriguez
2016-04-15 18:44 ` Stefano Stabellini
2016-04-06 11:07 ` George Dunlap
2016-04-06 15:02 ` Matt Fleming
[not found] ` <20160406160516.GC23684@char.us.oracle.com>
[not found] ` <20160406162347.GD23684@char.us.oracle.com>
2016-04-08 21:53 ` Luis R. Rodriguez
2016-04-13 10:03 ` Roger Pau Monné
2016-04-13 10:21 ` Matt Fleming
2016-04-07 18:51 ` Luis R. Rodriguez
2016-04-08 14:16 ` George Dunlap
2016-04-08 21:58 ` Luis R. Rodriguez
2016-04-12 22:12 ` Luis R. Rodriguez
2016-04-13 10:05 ` George Dunlap
2016-04-13 18:54 ` Luis R. Rodriguez
2016-04-14 9:42 ` George Dunlap
2016-04-14 19:59 ` Luis R. Rodriguez
2016-04-13 10:25 ` Roger Pau Monné
2016-04-13 19:10 ` Luis R. Rodriguez
2016-04-13 9:54 ` Roger Pau Monné
2016-04-13 18:50 ` Luis R. Rodriguez
[not found] ` <20160413190226.GB7501@char.us.oracle.com>
2016-04-13 19:14 ` Luis R. Rodriguez
[not found] ` <20160413192223.GA19026@char.us.oracle.com>
2016-04-13 20:01 ` Luis R. Rodriguez
[not found] ` <20160413201120.GA29797@char.us.oracle.com>
2016-04-13 20:35 ` Luis R. Rodriguez
2016-04-14 10:13 ` George Dunlap
2016-04-13 15:44 ` George Dunlap
2016-04-13 19:52 ` Luis R. Rodriguez
2016-04-14 9:53 ` George Dunlap
2016-04-14 19:44 ` Luis R. Rodriguez [this message]
2016-04-14 20:38 ` Konrad Rzeszutek Wilk
2016-04-14 21:12 ` Luis R. Rodriguez
2016-04-15 2:14 ` Konrad Rzeszutek Wilk
2016-04-15 5:50 ` Juergen Gross
2016-04-15 15:24 ` Luis R. Rodriguez
2016-04-15 9:59 ` George Dunlap
2016-04-15 15:30 ` Luis R. Rodriguez
2016-04-15 16:03 ` George Dunlap
2016-04-15 17:17 ` Luis R. Rodriguez
2016-04-06 11:11 ` Daniel Kiper
2016-04-07 19:12 ` Luis R. Rodriguez
2016-04-09 17:02 ` Luis R. Rodriguez
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=20160414194408.GP1990@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=GLin@suse.com \
--cc=JBeulich@suse.com \
--cc=JCheung@suse.com \
--cc=MChang@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=carnold@suse.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=hpa@zytor.com \
--cc=jeffm@suse.com \
--cc=jfehlig@suse.com \
--cc=jgross@suse.com \
--cc=jlee@suse.com \
--cc=julien.grall@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=matt@codeblueprint.co.uk \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=vojtech@suse.cz \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox