mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 6/7] sched/rt: make it configurable
Date: Tue, 30 May 2017 10:41:15 +0200	[thread overview]
Message-ID: <20170530084115.chn47covtxlcktna@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170529210302.26868-7-nicolas.pitre@linaro.org>

On Mon, May 29, 2017 at 05:03:01PM -0400, Nicolas Pitre wrote:

> @@ -1303,8 +1303,17 @@ config SCHED_AUTOGROUP
>  	  desktop applications.  Task group autogeneration is currently based
>  	  upon task session.
>  
> +config SCHED_RT
> +	bool "Real Time Task Scheduling" if EXPERT
> +	default y
> +	help
> +	  This adds the sched_rt scheduling class to the kernel providing
> + 	  support for the SCHED_FIFO and SCHED_RR policies. You might want
> +	  to disable this to reduce the kernel size. If unsure say y.
> +
>  config SCHED_DL
>  	bool "Deadline Task Scheduling" if EXPERT
> +	depends on SCHED_RT
>  	default y
>  	help
>  	  This adds the sched_dl scheduling class to the kernel providing
> @@ -1632,6 +1641,7 @@ config BASE_FULL
>  config FUTEX
>  	bool "Enable futex support" if EXPERT
>  	default y
> +	depends on SCHED_RT
>  	select RT_MUTEXES
>  	help
>  	  Disabling this option will cause the kernel to be built without

Aside from all the other completely non-starter #ifdeffery trainwrecks,
this is just plain wrong.

  reply	other threads:[~2017-05-30  8:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 21:02 [PATCH 0/7] scheduler tinification Nicolas Pitre
2017-05-29 21:02 ` [PATCH 1/7] cpuset/sched: cpuset makes sense for SMP only Nicolas Pitre
2017-05-29 21:02 ` [PATCH 2/7] sched: omit stop_sched_class when !SMP Nicolas Pitre
2017-06-08  9:30   ` [tip:sched/core] sched/core: Omit building " tip-bot for Nicolas Pitre
2017-05-29 21:02 ` [PATCH 3/7] sched/deadline: move dl related code out of sched/core.c Nicolas Pitre
2017-05-29 21:02 ` [PATCH 4/7] sched/deadline: make it configurable Nicolas Pitre
2017-05-29 21:03 ` [PATCH 5/7] sched/rt: move rt related code out of sched/core.c Nicolas Pitre
2017-05-29 21:03 ` [PATCH 6/7] sched/rt: make it configurable Nicolas Pitre
2017-05-30  8:41   ` Peter Zijlstra [this message]
2017-05-30 12:17     ` Nicolas Pitre
2017-05-30 12:31       ` Peter Zijlstra
2017-05-31  2:18         ` Nicolas Pitre
2017-05-31  9:57         ` Daniel Bristot de Oliveira
2017-05-31 10:40           ` Peter Zijlstra
2017-05-31 16:06   ` [6/7] " Rob Herring
2017-05-31 16:25     ` Nicolas Pitre
2017-05-29 21:03 ` [PATCH 7/7] rtmutex: compatibility with CONFIG_SCHED_RT=n Nicolas Pitre
2017-05-30  8:32 ` [PATCH 0/7] scheduler tinification Peter Zijlstra

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=20170530084115.chn47covtxlcktna@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®