From: Ian Campbell <Ian.Campbell@citrix.com>
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>
Subject: Re: --enable-xsm ?
Date: Thu, 15 Jan 2015 09:40:45 +0000 [thread overview]
Message-ID: <1421314845.19103.303.camel@citrix.com> (raw)
In-Reply-To: <20150114183909.GB2013@l.oracle.com>
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.
next prev parent reply other threads:[~2015-01-15 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 19:27 --enable-xsm ? Konrad Rzeszutek Wilk
2015-01-13 20:43 ` Daniel De Graaf
2015-01-14 9:06 ` Jan Beulich
2015-01-14 18:39 ` Konrad Rzeszutek Wilk
2015-01-15 8:08 ` Jan Beulich
2015-01-15 9:40 ` Ian Campbell [this message]
2015-01-15 16:53 ` Don Slutz
2015-01-15 18:20 ` Konrad Rzeszutek Wilk
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=1421314845.19103.303.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=konrad.wilk@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.