>>> On 07.01.16 at 16:30, wrote:
> Some proposed text for discussion:
>
> config STANDARD_PLATFORM
> bool "Standard/Supported Platform"
> default y
> help
> This option enables everything which is part of the standard and
> supported Xen platform. You sho
>>> On 07.01.16 at 16:18, wrote:
> On 1/7/16 9:00 AM, Ian Campbell wrote:
>> If we invert the sense then we could call it e.g. CONFIG_STANDARD_PLATFORM
>> and default it to y, I expect it will be easier to discourage people from
>> turning such an option off than to discourage them from turning so
On Thu, 2016-01-07 at 07:37 -0700, Jan Beulich wrote:
> > > > On 07.01.16 at 15:01, wrote:
>
> > Ian Campbell writes:
> >
> > > I don't see this as contrary to your stated goals (e.g. ripping out all
> > > the
> > > other schedulers), but I consider you to be within the expert camp for
> > > wa
>>> On 07.01.16 at 15:01, wrote:
> Ian Campbell writes:
>
>> I don't see this as contrary to your stated goals (e.g. ripping out all the
>> other schedulers), but I consider you to be within the expert camp for
>> wanting to do so (and having the chops to handle whatever pieces you find
>> yours
On Fri, 2015-12-18 at 11:56 -0600, Doug Goldstein wrote:
> In the end I really see the primary people that build Xen on their own
> as project maintainers (XenServer, Qubes, OpenXT) or distro maintainers
> (Ubuntu, Debian, Gentoo, Yocto) or "expert" users. Most people will use
> Xen as it comes pac
On 18/12/15 17:56, Doug Goldstein wrote:
> On 12/18/15 4:45 AM, Ian Campbell wrote:
>> On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
>>> Add machinery to allow the schedulers to be individually selectable
>>> through the Kconfig interface.
>> So I don't want to pick on this series or
On 12/18/15 4:45 AM, Ian Campbell wrote:
> On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
>> Add machinery to allow the schedulers to be individually selectable
>> through the Kconfig interface.
>
> So I don't want to pick on this series or schedulers specifically here, but
> instead
On 18/12/15 12:30, Jan Beulich wrote:
On 18.12.15 at 12:08, wrote:
>> What I'd really like to see in the config options are things like:
>>
>> CONFIG_BIGMEM (instead of doing it via environment variable),
>> NR_CPUS, and possibly some other numerical bounds which won't select
>> a feature, bu
>>> On 18.12.15 at 12:08, wrote:
> What I'd really like to see in the config options are things like:
>
> CONFIG_BIGMEM (instead of doing it via environment variable),
> NR_CPUS, and possibly some other numerical bounds which won't select
> a feature, but might be interesting to change for huge s
On Fri, 2015-12-18 at 12:08 +0100, Juergen Gross wrote:
> On 18/12/15 11:45, Ian Campbell wrote:
> > On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
> > > Add machinery to allow the schedulers to be individually selectable
> > > through the Kconfig interface.
> >
> > So I don't want t
On 18/12/15 11:45, Ian Campbell wrote:
> On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
>> Add machinery to allow the schedulers to be individually selectable
>> through the Kconfig interface.
>
> So I don't want to pick on this series or schedulers specifically here, but
> instead d
>>> On 18.12.15 at 11:45, wrote:
> How would people feel about a CONFIG_STANDARD_FEATURESET[0] with the
> majority of tweakables depending on !STANDARD_FEATURESET? It would default
> Y with a help text which dissuades normal users from touching it ("Say Y,
> unless you are willing to pick up the p
On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
> Add machinery to allow the schedulers to be individually selectable
> through the Kconfig interface.
So I don't want to pick on this series or schedulers specifically here, but
instead discuss the general premise of configurability of
>>> On 17.12.15 at 21:59, 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,
14 matches
Mail list logo
