From: George Dunlap <george.dunlap@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
Jonathan Creekmore <jonathan.creekmore@gmail.com>,
xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: [PATCH 1/4] build: Hook the schedulers into Kconfig
Date: Fri, 18 Dec 2015 10:52:50 +0000 [thread overview]
Message-ID: <5673E582.6030000@citrix.com> (raw)
In-Reply-To: <1450402503.19320.97.camel@citrix.com>
On 18/12/15 01:35, Dario Faggioli wrote:
> On Thu, 2015-12-17 at 14:59 -0600, Jonathan Creekmore wrote:
>> Allow the schedulers to be independently enabled or disabled at
>> compile-time instead of just allowing the scheduler to be selected on
>> the command line.
>>
> Reading this quickly, that "instead" gave me a bit of an hard time. I'm
> not a native English speaker, and I'm sure it's me that am wrong, but
> for some reason the sentence made me think that the patch would somehow
> disallow specifying a scheduler during boot, in Xen's command line.
I think the "just" in the sentence is an attempt to disambiguate (i.e.,
instead of *only* allowing the scheduler to be chosen on the
command-line, *also* allow it to be chosen at compile-time).
But I agree that the whole clause isn't really necessary and it would be
clearer without it.
-George
>
> Fact is, I don't think the phrase "instead of just allowing the
> scheduler to be selected on the command line." adds much information,
> and I'd just remove it.
>
>> To match existing behavior, all four schedulers are
>> compiled in by default, although the RTDS and ARINC653 are marked
>> EXPERIMENTAL to match their not currently supported status.
>>
> This may change shortly, but as of now, Credit2 is still experimental
> too. I think I'd still recommend enabling it in the help file (i.e.,
> I'm ok with "If unsure, say Y"), but we certainly should mark it with
> "(EPERIMENTAL)".
>
> I don't know much on how kconfig works, so all the changes to the
> makefile, etc, I'm not able to review them properly.
>
> On the other hand, the code here below...
>
>> --- a/xen/common/schedule.c
>> +++ b/xen/common/schedule.c
>> @@ -38,8 +38,8 @@
>> #include <public/sched.h>
>> #include <xsm/xsm.h>
>>
>> -/* opt_sched: scheduler - default to credit */
>> -static char __initdata opt_sched[10] = "credit";
>> +/* opt_sched: scheduler - default to configured value */
>> +static char __initdata opt_sched[10] = CONFIG_SCHED_DEFAULT;
>> string_param("sched", opt_sched);
>>
>> /* if sched_smt_power_savings is set,
>> @@ -65,10 +65,18 @@ DEFINE_PER_CPU(struct schedule_data,
>> schedule_data);
>> DEFINE_PER_CPU(struct scheduler *, scheduler);
>>
>> static const struct scheduler *schedulers[] = {
>> +#ifdef CONFIG_SCHED_CREDIT
>> &sched_credit_def,
>> +#endif
>> +#ifdef CONFIG_SCHED_CREDIT2
>> &sched_credit2_def,
>> +#endif
>> +#ifdef CONFIG_SCHED_ARINC653
>> &sched_arinc653_def,
>> +#endif
>> +#ifdef CONFIG_SCHED_RTDS
>> &sched_rtds_def,
>> +#endif
>> };
>>
> ... can have, with the changelog changed as shown, my:
>
> Acked-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Regards,
> Daio
>
next prev parent reply other threads:[~2015-12-18 10:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 20:59 [PATCH 0/4] Allow schedulers to be selectable through Kconfig Jonathan Creekmore
2015-12-17 20:59 ` [PATCH 1/4] build: Hook the schedulers into Kconfig Jonathan Creekmore
2015-12-18 1:35 ` Dario Faggioli
2015-12-18 2:20 ` Jonathan Creekmore
2015-12-18 9:19 ` Dario Faggioli
2015-12-18 10:52 ` George Dunlap [this message]
2015-12-18 11:23 ` Dario Faggioli
2015-12-18 8:57 ` Andrew Cooper
2015-12-18 16:43 ` Jonathan Creekmore
2015-12-17 20:59 ` [PATCH 2/4] build: Alloc space for sched list in the link file Jonathan Creekmore
2015-12-18 9:01 ` Andrew Cooper
2015-12-18 16:40 ` Jonathan Creekmore
2015-12-18 16:48 ` Andrew Cooper
2015-12-18 17:07 ` Jan Beulich
2015-12-18 17:10 ` Andrew Cooper
2015-12-18 17:11 ` Jonathan Creekmore
2015-12-18 17:23 ` Andrew Cooper
2015-12-17 20:59 ` [PATCH 3/4] sched: Register the schedulers into the list Jonathan Creekmore
2015-12-18 1:42 ` Dario Faggioli
2015-12-18 9:03 ` Andrew Cooper
2015-12-17 20:59 ` [PATCH 4/4] sched: Use the auto-generated list of schedulers Jonathan Creekmore
2015-12-18 1:47 ` Dario Faggioli
2015-12-18 9:12 ` Andrew Cooper
2015-12-18 16:44 ` Jonathan Creekmore
2015-12-18 10:50 ` Jan Beulich
2015-12-18 16:00 ` Jonathan Creekmore
2015-12-18 16:43 ` Jan Beulich
2015-12-18 17:24 ` Jonathan Creekmore
2015-12-18 17:30 ` Andrew Cooper
2015-12-18 10:39 ` [PATCH 0/4] Allow schedulers to be selectable through Kconfig Jan Beulich
2015-12-18 10:45 ` Ian Campbell
2015-12-18 10:58 ` Jan Beulich
2015-12-18 11:08 ` Juergen Gross
2015-12-18 11:19 ` Ian Campbell
2015-12-18 11:30 ` Jan Beulich
[not found] ` <5673FC6202000078000C122B@suse.com>
2015-12-18 11:41 ` Juergen Gross
2015-12-18 17:56 ` Doug Goldstein
2015-12-18 18:25 ` Andrew Cooper
2016-01-06 14:45 ` Ian Campbell
2016-01-07 14:01 ` Jonathan Creekmore
2016-01-07 14:37 ` Jan Beulich
2016-01-07 15:00 ` Ian Campbell
2016-01-07 15:18 ` Doug Goldstein
2016-01-07 15:31 ` Ian Campbell
2016-01-07 15:43 ` Jonathan Creekmore
2016-01-07 15:54 ` Jan Beulich
2016-01-07 15:47 ` Jan Beulich
2016-01-07 15:30 ` Ian Campbell
2016-01-07 15:51 ` Jan Beulich
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=5673E582.6030000@citrix.com \
--to=george.dunlap@citrix.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).