Re: [PATCH 0/4] Allow schedulers to be selectable through Kconfig

From: "Jan Beulich" <JBeulich@suse.com>
To: Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/4] Allow schedulers to be selectable through Kconfig
Date: Fri, 18 Dec 2015 03:39:10 -0700	[thread overview]
Message-ID: <5673F05E02000078000C1179@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1450385974-12732-1-git-send-email-jonathan.creekmore@gmail.com>

>>> On 17.12.15 at 21:59, <jonathan.creekmore@gmail.com> wrote:
> Add machinery to allow the schedulers to be individually selectable
> through the Kconfig interface. The first patch in the series sets up
> the Kconfig options for the schedulers and places the appropriate CONFIG_
> options around the scheduler list. The second, third, and fourth patches
> rework the scheduler list from being manually curated into a model
> where just compiling any schedulers into the hypervisor causes the
> scheduler list to be built up.

This is very quickly moving us into a direction that previous
discussion indicated we don't want to move into right away:
A multitude of different configurations that people may be
using. Granted selecting schedulers is pretty self contained,
but if we allow this, where would we draw the line? At the
very least you should have Cc-ed people involved in that
original discussion and having indicated opposition to that
direction.

Jan