From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753463AbcDNJxz (ORCPT ); Thu, 14 Apr 2016 05:53:55 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:22397 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751205AbcDNJxx (ORCPT ); Thu, 14 Apr 2016 05:53:53 -0400 X-IronPort-AV: E=Sophos;i="5.24,484,1454976000"; d="scan'208";a="353678002" Subject: Re: [Xen-devel] HVMLite / PVHv2 - using x86 EFI boot entry To: "Luis R. Rodriguez" References: <20160406024027.GX1990@wotan.suse.de> <20160407185148.GL1990@wotan.suse.de> <20160413195257.GB1990@wotan.suse.de> CC: Matt Fleming , , Michael Chang , Linux Kernel Mailing List , Jim Fehlig , Jan Beulich , "H. Peter Anvin" , Daniel Kiper , "the arch/x86 maintainers" , Takashi Iwai , =?UTF-8?Q?Vojt=c4=9bch_Pavl=c3=adk?= , Gary Lin , xen-devel , Jeffrey Cheung , Juergen Gross , Stefano Stabellini , joeyli , Borislav Petkov , Boris Ostrovsky , Charles Arndol , Andrew Cooper , Julien Grall , Andy Lutomirski , David Vrabel , Linus Torvalds , =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= From: George Dunlap Message-ID: <570F68AB.2040400@citrix.com> Date: Thu, 14 Apr 2016 10:53:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160413195257.GB1990@wotan.suse.de> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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. 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. -George