From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: --enable-xsm ?
Date: Thu, 15 Jan 2015 09:40:45 +0000
Message-ID: <1421314845.19103.303.camel@citrix.com>
References: <20150113192758.GA30253@localhost.localdomain>
	<54B5838A.5020205@tycho.nsa.gov>
	<54B63FAD0200007800054A4C@mail.emea.novell.com>
	<20150114183909.GB2013@l.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1YBgv6-0004eh-5I
	for xen-devel@lists.xenproject.org; Thu, 15 Jan 2015 09:40:52 +0000
In-Reply-To: <20150114183909.GB2013@l.oracle.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: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, Daniel De Graaf <dgdegra@tycho.nsa.gov>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2015-01-14 at 13:39 -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 14, 2015 at 09:06:37AM +0000, Jan Beulich wrote:
> > >>> On 13.01.15 at 21:43, <dgdegra@tycho.nsa.gov> wrote:
> > > On 01/13/2015 02:27 PM, Konrad Rzeszutek Wilk wrote:
> > >> I was wondering if there would be any plans for configure.ac
> > >> (or the m4 scripts) to have an --enable-xsm which would set
> > >> XSM_ENABLE (or FLASK_ENABLE) to true?
> > >>
> > >> Right now by default to build with XSM one has to manually change
> > >> the Config.mk ENABLE_XSM option to 'y'.
> > > 
> > > Is the hypervisor build allowed to depend on having run ./configure
> > > now?  I think this was the reason why config.mk is being used.
> > 
> > Correct - configury only controls the tools (and stubdom iirc).
> 
> Ah that is right. Should we expand on that then? Make the hypervisor
> build with different configure options?

The hypervisor maintainers have indicated repeatedly that they do not
want building the hypervisor to require running configure. Which makes
sense, since Xen has no dependency on the userspace environment.

Ian.