From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] 4.4-rc6-rt1
Date: Fri, 22 Jan 2016 21:44:09 +0100 [thread overview]
Message-ID: <20160122204409.GB3883@linutronix.de> (raw)
In-Reply-To: <56A24F39.2050606@linutronix.de>
* Sebastian Andrzej Siewior | 2016-01-22 16:48:09 [+0100]:
>On 01/22/2016 04:35 PM, Grygorii Strashko wrote:
>> Additional note: RCU_BOOST now depends on RCU_EXPERT, so commit
>> 3da4cab "rcu: make RCU_BOOST default on RT" is nop now.
>>
>> config RCU_BOOST
>> bool "Enable RCU priority boosting"
>> depends on RT_MUTEXES && PREEMPT_RCU && RCU_EXPERT
>> default y if PREEMPT_RT_FULL
>
>yeah, I've been thinking about giving the experts menu item an y on RT
>as well.
Subject: [PATCH] RCU: make RCU_EXPERT y on RT
because we want RCU_BOOST y on RT
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 6f4408adf62d..a7c81c0911da 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -498,7 +498,7 @@ config TINY_RCU
config RCU_EXPERT
bool "Make expert-level adjustments to RCU configuration"
- default n
+ default y if PREEMPT_RT_FULL
help
This option needs to be enabled if you wish to make
expert-level adjustments to RCU configuration. By default,
--
2.7.0.rc3
prev parent reply other threads:[~2016-01-22 20:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 22:57 [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior
2015-12-31 16:24 ` Clark Williams
2016-01-01 7:19 ` Mike Galbraith
2016-01-01 9:14 ` Thomas Gleixner
2016-01-01 9:45 ` Mike Galbraith
[not found] ` <568CF08F.3070001@caviumnetworks.com>
2016-01-13 11:45 ` [ANNOUNCE] 4.4-rc6-rt1 (arm64) Jaggi, Manish
2016-01-13 13:45 ` Sebastian Andrzej Siewior
2016-01-14 11:50 ` Jaggi, Manish
2016-01-13 17:58 ` [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior
2016-01-13 18:36 ` Grygorii Strashko
2016-01-14 14:59 ` Sebastian Andrzej Siewior
2016-01-14 9:33 ` Mike Galbraith
2016-01-14 14:17 ` Sebastian Andrzej Siewior
2016-01-14 14:29 ` Mike Galbraith
2016-01-14 14:30 ` Thomas Gleixner
2016-01-14 14:57 ` Mike Galbraith
2016-01-14 15:07 ` Thomas Gleixner
2016-01-14 16:05 ` Mike Galbraith
2016-01-16 13:23 ` Mike Galbraith
2016-01-16 13:43 ` Thomas Gleixner
2016-01-16 13:52 ` Mike Galbraith
2016-01-16 13:59 ` Thomas Gleixner
2016-01-16 14:09 ` Mike Galbraith
2016-01-07 12:15 ` Tim Sander
2016-01-13 13:40 ` Sebastian Andrzej Siewior
2016-01-22 15:35 ` Grygorii Strashko
2016-01-22 15:48 ` Sebastian Andrzej Siewior
2016-01-22 20:44 ` Sebastian Andrzej Siewior [this message]
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=20160122204409.GB3883@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).