From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH v5 2/5] build: Hook the schedulers into Kconfig
Date: Thu, 14 Jan 2016 16:58:21 +0000 [thread overview]
Message-ID: <1452790701.32341.17.camel@citrix.com> (raw)
In-Reply-To: <5697DE6F02000078000C6E6D@prv-mh.provo.novell.com>
On Thu, 2016-01-14 at 09:44 -0700, Jan Beulich wrote:
> > > > On 14.01.16 at 17:34, <ian.campbell@citrix.com> wrote:
> > On Thu, 2016-01-14 at 10:23 -0600, Jonathan Creekmore wrote:
> > > Jan Beulich writes:
> > >
> > > > > > > On 14.01.16 at 15:49, <jonathan.creekmore@gmail.com> wrote:
> > > > > --- a/xen/common/Kconfig
> > > > > +++ b/xen/common/Kconfig
> > > > > @@ -51,4 +51,63 @@ config KEXEC
> > > > >
> > > > > If unsure, say Y.
> > > > >
> > > > > +# Enable schedulers
> > > > > +menu "Schedulers"
> > > > > + visible if EXPERT = "y"
> > > > > +
> > > > > +config SCHED_CREDIT
> > > > > + bool
> > > > > + default y
> > > > > + ---help---
> > > > > + The traditional credit scheduler is a general purpose
> > > > > scheduler.
> > > >
> > > > So is this option now useful for anything?
> > >
> > > It keeps the code between all of the schedulers consistent (all of
> > > them
> > > have a #define if they are compiled it)
> >
> > FWIW I think this (consistency) is a reasonable argument for having
> > this
> > option even if it doesn't actually do anything.
>
> While I can see your point, I dislike useless clutter in .config (also
> on Linux, where I every once in a while send some cleanup
> patches).
I don't think this one is useless clutter, it provides useful information
to someone looking at the .config rather than then having to go and check
the source to find out what the defaults were.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-14 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 14:49 [PATCH v5 0/5] Allow schedulers to be selectable through Kconfig Jonathan Creekmore
2016-01-14 14:49 ` [PATCH v5 1/5] build: Env var to enable expert config options Jonathan Creekmore
2016-01-14 16:09 ` Jan Beulich
2016-01-15 15:47 ` Ian Campbell
2016-01-15 16:56 ` Jan Beulich
2016-01-14 14:49 ` [PATCH v5 2/5] build: Hook the schedulers into Kconfig Jonathan Creekmore
2016-01-14 16:13 ` Jan Beulich
2016-01-14 16:23 ` Jonathan Creekmore
2016-01-14 16:34 ` Ian Campbell
2016-01-14 16:44 ` Jan Beulich
2016-01-14 16:58 ` Ian Campbell [this message]
2016-01-14 17:22 ` Jonathan Creekmore
2016-01-14 14:49 ` [PATCH v5 3/5] build: Alloc space for sched list in the link file Jonathan Creekmore
2016-01-14 14:49 ` [PATCH v5 4/5] sched: Register the schedulers into the list Jonathan Creekmore
2016-01-14 14:49 ` [PATCH v5 5/5] sched: Use the auto-generated list of schedulers Jonathan Creekmore
2016-01-14 16:17 ` Jan Beulich
2016-01-14 16:25 ` Jonathan Creekmore
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=1452790701.32341.17.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jonathan.creekmore@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).