* --enable-xsm ? @ 2015-01-13 19:27 Konrad Rzeszutek Wilk 2015-01-13 20:43 ` Daniel De Graaf 0 siblings, 1 reply; 8+ messages in thread From: Konrad Rzeszutek Wilk @ 2015-01-13 19:27 UTC (permalink / raw) To: dgdegra, xen-devel Hey 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'. Thanks. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 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 0 siblings, 1 reply; 8+ messages in thread From: Daniel De Graaf @ 2015-01-13 20:43 UTC (permalink / raw) To: Konrad Rzeszutek Wilk, xen-devel On 01/13/2015 02:27 PM, Konrad Rzeszutek Wilk wrote: > Hey > > 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'. > > Thanks. Is the hypervisor build allowed to depend on having run ./configure now? I think this was the reason why config.mk is being used. -- Daniel De Graaf National Security Agency ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 2015-01-13 20:43 ` Daniel De Graaf @ 2015-01-14 9:06 ` Jan Beulich 2015-01-14 18:39 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 8+ messages in thread From: Jan Beulich @ 2015-01-14 9:06 UTC (permalink / raw) To: Konrad Rzeszutek Wilk, Daniel De Graaf; +Cc: xen-devel >>> 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). Jan ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 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 0 siblings, 2 replies; 8+ messages in thread From: Konrad Rzeszutek Wilk @ 2015-01-14 18:39 UTC (permalink / raw) To: Jan Beulich; +Cc: xen-devel, Daniel De Graaf 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? > > Jan > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 2015-01-14 18:39 ` Konrad Rzeszutek Wilk @ 2015-01-15 8:08 ` Jan Beulich 2015-01-15 9:40 ` Ian Campbell 1 sibling, 0 replies; 8+ messages in thread From: Jan Beulich @ 2015-01-15 8:08 UTC (permalink / raw) To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Daniel De Graaf >>> On 14.01.15 at 19:39, <konrad.wilk@oracle.com> 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? I'd really try to avoid that; if any configuration should be needed, it should rather follow e.g. the Linux kernel model than the user space one used for the tools. Jan ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 2015-01-14 18:39 ` Konrad Rzeszutek Wilk 2015-01-15 8:08 ` Jan Beulich @ 2015-01-15 9:40 ` Ian Campbell 2015-01-15 16:53 ` Don Slutz 1 sibling, 1 reply; 8+ messages in thread From: Ian Campbell @ 2015-01-15 9:40 UTC (permalink / raw) To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Daniel De Graaf, Jan Beulich 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. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 2015-01-15 9:40 ` Ian Campbell @ 2015-01-15 16:53 ` Don Slutz 2015-01-15 18:20 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 8+ messages in thread From: Don Slutz @ 2015-01-15 16:53 UTC (permalink / raw) To: Ian Campbell, Konrad Rzeszutek Wilk Cc: xen-devel, Daniel De Graaf, Jan Beulich On 01/15/15 04:40, Ian Campbell wrote: > 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'. This is not strictly true. I see the option as XSM_ENABLE. And docs/misc/xsm-flask.txt correctly states that a .config file can specify this. Also you can add XSM_ENABLE=y to the make command line. And in bash, export XSM_ENABLE=y works. All of these work without a manual change to Config.mk -Don Slutz >>>> 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. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: --enable-xsm ? 2015-01-15 16:53 ` Don Slutz @ 2015-01-15 18:20 ` Konrad Rzeszutek Wilk 0 siblings, 0 replies; 8+ messages in thread From: Konrad Rzeszutek Wilk @ 2015-01-15 18:20 UTC (permalink / raw) To: Don Slutz; +Cc: xen-devel, Daniel De Graaf, Ian Campbell, Jan Beulich On Thu, Jan 15, 2015 at 11:53:20AM -0500, Don Slutz wrote: > On 01/15/15 04:40, Ian Campbell wrote: > >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'. > > This is not strictly true. I see the option as XSM_ENABLE. And > > docs/misc/xsm-flask.txt > > correctly states that a .config file can specify this. Also you can add > XSM_ENABLE=y to the make command line. > > And in bash, export XSM_ENABLE=y works. All of these work without > a manual change to Config.mk That is right. I totally forgot about that :-) Will use that to make sure I build with XSM enabled. Thanks! ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-01-15 18:20 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2015-01-15 16:53 ` Don Slutz 2015-01-15 18:20 ` Konrad Rzeszutek Wilk
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.