From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] build: save generated config in /boot
Date: Wed, 6 Jan 2016 10:31:17 +0000
Message-ID: <1452076277.7292.17.camel@citrix.com>
References: <1450474548-26428-1-git-send-email-cardoe@cardoe.com>
	<5677FA9802000078000C1DA7@prv-mh.provo.novell.com>
	<56780E25.9090806@cardoe.com>
	<56781FFA02000078000C1F3D@prv-mh.provo.novell.com>
	<567818B3.6060908@cardoe.com>
	<56782A4402000078000C1FD0@prv-mh.provo.novell.com>
	<567945F9.7040109@cardoe.com>
	<5679558002000078000C23CE@prv-mh.provo.novell.com>
	<56796237.4090102@citrix.com>
	<5679818402000078000C253F@prv-mh.provo.novell.com>
	<5679740E.9090309@cardoe.com>
	<567983C302000078000C255F@prv-mh.provo.novell.com>
	<568BF504.1030205@cardoe.com>
	<568CEAFB02000078000C3D0F@prv-mh.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <568CEAFB02000078000C3D0F@prv-mh.provo.novell.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: Jan Beulich <JBeulich@suse.com>, Doug Goldstein <cardoe@cardoe.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2016-01-06 at 02:22 -0700, Jan Beulich wrote:
> > > > On 05.01.16 at 17:53, <cardoe@cardoe.com> wrote:
> > On 12/22/15 10:09 AM, Jan Beulich wrote:
> > > > > > On 22.12.15 at 17:02, <cardoe@cardoe.com> wrote:
> > > > How does it not make sense in this case? That's what Andrew and I
> > > > are
> > > > asking you to explain.
> > > 
> > > But I already explained it: The file isn't needed for booting.
> > 
> > One use of it in /boot would be to check the file in 20_linux_xen like
> > we check the kernel config for different options to add different
> > parameters.
> 
> Which, if you search for it, is a very controversial thing: I agree
> with the side demanding for grub to not inspect the kernel's
> .config.

What is the preferred mechanism for determining from the contents of /boot
whether an XSM entry should be produced or not?

Ian.