From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH OSSTEST v3 21/22] Debian: Arrange to be able
 to chainload a xen.efi from grub2
Date: Thu, 25 Jun 2015 13:31:41 -0400
Message-ID: <20150625173141.GD2470@x230.dumpdata.com>
References: <1435159944.28264.295.camel@citrix.com>
	<1435159961-22292-21-git-send-email-ian.campbell@citrix.com>
	<21899.55559.43212.817471@mariner.uk.xensource.com>
	<1435232772.32500.49.camel@citrix.com>
	<21899.62925.356920.56798@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <21899.62925.356920.56798@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On Thu, Jun 25, 2015 at 01:36:29PM +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v3 21/22] Debian: Arrange to be able to chainload a xen.efi from grub2"):
> > On Thu, 2015-06-25 at 11:33 +0100, Ian Jackson wrote:
> > > Is there some upstream-friendly way of achieving the same thing ?
> > 
> > Not AFAIK. I could try upstreaming this but given that a) the user still
> > needs to manually copy things to the ESP and create a suitable xen.cfg
> > and b) people are working on a better way which will just work with the
> > existing non-UEFI grub.cfg file entries, I'm not sure how much point
> > there is.
> 
> I think "people are working on a better way" is what I was looking
> for.  When that change comes along, we can remove 20_linux_xen ?

Not sure if he speaks of Daniel and me doing things in that arena?

There is one outstanding patch for 20_linux_xen that adds the proper
'multiboot2' for the Xen?
> 
> > > I'm not really sure what is `specific to us' (or what `us' here means
> > > - osstest, or Xen on arm64, or ...?)
> > 
> > All the paths are basically specific to us, just the general shape of
> > the entry is more generically applicable.
> 
> `us' = osstest ?  Xen ?
> 
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel