[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH] xen: sched: use default scheduler upon an invalid "sched="
instead of just the first scheduler we find in the array. In fact, right now, if someone makes a typo when passing the "sched=" command line option to Xen, we (with all schedulers configured in) pick ARINC653, which is most likely not what one would expect. Go for the default scheduler instead. Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> --- Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx> Cc: Jan Beulich <jbeulich@xxxxxxxx> Cc: Doug Goldstein <cardoe@xxxxxxxxxx> Cc: Jonathan Creekmore <jonathan.creekmore@xxxxxxxxx> --- I don't think I'm going to ask for this to be put in 4.7, as I don't want to give Wei an heart attack... :-) Considering it for backporting should be enough, IMO. --- xen/common/schedule.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xen/common/schedule.c b/xen/common/schedule.c index 5e35310..7ac12d3 100644 --- a/xen/common/schedule.c +++ b/xen/common/schedule.c @@ -1625,7 +1625,8 @@ void __init scheduler_init(void) { printk("Could not find scheduler: %s\n", opt_sched); for ( i = 0; i < NUM_SCHEDULERS; i++ ) - if ( schedulers[i] ) + if ( schedulers[i] && + !strcmp(schedulers[i]->opt_name, CONFIG_SCHED_DEFAULT) ) { ops = *schedulers[i]; break; _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |