Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-11 Thread Jan Beulich
>>> On 08.01.16 at 17:58, wrote: > On 1/8/16 10:49 AM, Jan Beulich wrote: > On 08.01.16 at 17:30, wrote: >>> So, based on the Kconfig setup and the linker ASSERT, there should be no >>> way to have a default scheduler that is not in the build.

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Konrad Rzeszutek Wilk
On Fri, Jan 08, 2016 at 11:04:56AM -0600, Jonathan Creekmore wrote: > > Doug Goldstein writes: > > > On 1/8/16 10:49 AM, Jan Beulich wrote: > > On 08.01.16 at 17:30, wrote: > >>> So, based on the Kconfig setup and the linker ASSERT, there should be no > >>> way

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Jonathan Creekmore
Juergen Gross writes: > On 08/01/16 17:02, Jonathan Creekmore wrote: >> >> Andrew Cooper writes: >> >>> On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote: On Thu, Jan 07, 2016 at 11:29:18AM -0600, Jonathan Creekmore wrote: > Allow the schedulers to be independently enabled or disabled at

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Jonathan Creekmore
Doug Goldstein writes: > On 1/8/16 10:49 AM, Jan Beulich wrote: > On 08.01.16 at 17:30, wrote: >>> So, based on the Kconfig setup and the linker ASSERT, there should be no >>> way to have a default scheduler that is not in the build. I wish Kconfig >>> allowed

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Andrew Cooper
On 08/01/16 17:04, Jonathan Creekmore wrote: > Doug Goldstein writes: > >> On 1/8/16 10:49 AM, Jan Beulich wrote: >> On 08.01.16 at 17:30, wrote: So, based on the Kconfig setup and the linker ASSERT, there should be no way to have a default scheduler

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Konrad Rzeszutek Wilk
On Thu, Jan 07, 2016 at 11:29:18AM -0600, Jonathan Creekmore wrote: > Allow the schedulers to be independently enabled or disabled at > compile-time. To match existing behavior, all four schedulers are > compiled in by default, although the Credit2, RTDS, and ARINC653 are > marked EXPERIMENTAL to

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Juergen Gross
On 08/01/16 17:02, Jonathan Creekmore wrote: > > Andrew Cooper writes: > >> On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote: >>> On Thu, Jan 07, 2016 at 11:29:18AM -0600, Jonathan Creekmore wrote: Allow the schedulers to be independently enabled or disabled at compile-time. To match

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Dario Faggioli
On Fri, 2016-01-08 at 15:54 +, Andrew Cooper wrote: > On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote: > >  > > And the hypervisor did build with: > > > > [konrad@char xen]$ nm --defined xen-syms |grep schedulers > > 82d080290d58 D __end_schedulers_array > > 82d080290d58 D

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Doug Goldstein
On 1/8/16 10:49 AM, Jan Beulich wrote: On 08.01.16 at 17:30, wrote: >> So, based on the Kconfig setup and the linker ASSERT, there should be no >> way to have a default scheduler that is not in the build. I wish Kconfig >> allowed you to state that you must have

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Andrew Cooper
On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote: > On Thu, Jan 07, 2016 at 11:29:18AM -0600, Jonathan Creekmore wrote: >> Allow the schedulers to be independently enabled or disabled at >> compile-time. To match existing behavior, all four schedulers are >> compiled in by default, although the

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Jonathan Creekmore
Andrew Cooper writes: > On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote: >> On Thu, Jan 07, 2016 at 11:29:18AM -0600, Jonathan Creekmore wrote: >>> Allow the schedulers to be independently enabled or disabled at >>> compile-time. To match existing behavior, all four schedulers are >>> compiled in

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Jan Beulich
>>> On 08.01.16 at 17:13, wrote: > I think there should be an ASSERT (or some other measure) to > ensure the default scheduler is available. Indeed I was about to say exactly this. Jan ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-08 Thread Jan Beulich
>>> On 08.01.16 at 17:30, wrote: > So, based on the Kconfig setup and the linker ASSERT, there should be no > way to have a default scheduler that is not in the build. I wish Kconfig > allowed you to state that you must have at least one option selected or > up to

[Xen-devel] [PATCH v3 2/5] build: Hook the schedulers into Kconfig

2016-01-07 Thread Jonathan Creekmore
Allow the schedulers to be independently enabled or disabled at compile-time. To match existing behavior, all four schedulers are compiled in by default, although the Credit2, RTDS, and ARINC653 are marked EXPERIMENTAL to match their not currently supported status. CC: George Dunlap