From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [ANNOUNCE] 3.0-rt6
Date: Fri, 29 Jul 2011 07:03:07 -0700 [thread overview]
Message-ID: <20110729140307.GB2460@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107282213000.31246@ionos>
On Thu, Jul 28, 2011 at 11:43:16PM +0200, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0-rt6 release.
>
> Changes versus 3.0-rt4 (I pushed out a rt5 w/o announce)
>
> * pin_cpu fix (Yong Zhang)
>
> * Various compile fixes (Yong Zhang & myself)
>
> * Serial fix for omap
>
> * Clocksource lockless watchdog reset
>
> * Reenabled CONFIG_RCU_BOOST (problem is unreproducible and maybe
> related to NO_HZ, which is still disabled. Paul is working on it!)
Once I remembered to fill in the CONFIG_INITRAMFS_SOURCE kernel parameter,
-rt6 booted just fine with CONFIG_RCU_BOOST=y and CONFIG_NO_HZ=y.
(Before that, the init process was whining bitterly about life in
general and segmentation faults in particular.) There are dyntick-idle
periods happening, as can be seen from the first one-third of debugfs's
rcu/rcudata file:
rcu_preempt:
0 c=225221 g=225222 pq=1 pqc=225221 qp=1 dt=7363/1/0 df=387 of=0 ri=0 ql=2 qs=..W. kt=0/W/0 ktl=96cc b=10 ci=2148054 co=0 ca=0
1 c=225221 g=225222 pq=1 pqc=225221 qp=1 dt=11677/1/0 df=1381 of=0 ri=0 ql=0 qs=.... kt=0/W/1 ktl=ba97 b=10 ci=1089926 co=0 ca=0
The dt= fields count the number of times the corresponding CPU has
transitioned to and from dyntick-idle mode. There is also some RCU
priority boosting happening:
0:7 tasks=TN.. kt=W ntb=3 neb=0 nnb=3 j=1182 bt=12fc
balk: nt=0 egt=1750 bt=37 nb=2 ny=311044 nos=0
The ntb= field tells us that there have been three priority-boost events,
and nnb= tells us that they have all been for normal (as opposed to
expedited) grace periods. You need CONFIG_RCU_TRACE=y to enable these,
in case you want to see them yourself.
This has survived 45 minutes of rcutorture thus far.
It might well be that a two-CPU 32-bit x86 environment is especially
kind to -rt, but I nevertheless propose the following patch.
Thanx, Paul
------------------------------------------------------------------------
nohz: Enable CONFIG_NO_HZ in -rt kernel builds
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
Kconfig | 1 -
1 file changed, 1 deletion(-)
diff -urpNa -X dontdiff linux-3.0-rt5/kernel/time/Kconfig linux-3.0-rt6/kernel/time/Kconfig
--- linux-3.0-rt5/kernel/time/Kconfig 2011-07-28 15:47:04.000000000 -0700
+++ linux-3.0-rt6/kernel/time/Kconfig 2011-07-29 04:31:06.000000000 -0700
@@ -7,7 +7,6 @@ config TICK_ONESHOT
config NO_HZ
bool "Tickless System (Dynamic Ticks)"
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
- depends on !PREEMPT_RT_FULL
select TICK_ONESHOT
help
This option enables a tickless system: timer interrupts will
next prev parent reply other threads:[~2011-07-29 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 21:43 [ANNOUNCE] 3.0-rt6 Thomas Gleixner
2011-07-28 23:33 ` Peter W. Morreale
2011-07-29 0:56 ` Thomas Gleixner
2011-07-29 6:05 ` Mike Galbraith
2011-07-29 14:03 ` Paul E. McKenney [this message]
2011-07-29 15:57 ` [ANNOUNCE] 3.0-rt6 (kgdb working) Darren Hart
2011-07-30 15:49 ` [ANNOUNCE] 3.0-rt6 Remy Bohmer
2011-07-30 20:21 ` Remy Bohmer
2011-08-07 10:44 ` Remy Bohmer
2011-08-01 8:42 ` Rolando Martins
2011-08-01 10:34 ` Mike Galbraith
2011-08-01 10:45 ` Rolando Martins
2011-08-01 11:06 ` Peter Zijlstra
2011-08-01 11:10 ` Rolando Martins
2011-08-04 6:34 ` Fernando Lopez-Lezcano
2011-08-04 9:42 ` Peter Zijlstra
2011-08-04 19:05 ` Fernando Lopez-Lezcano
2011-08-04 20:15 ` Uwe Kleine-König
2011-08-05 9:28 ` Uwe Kleine-König
2011-08-05 16:03 ` Fernando Lopez-Lezcano
2011-08-08 17:25 ` Fernando Lopez-Lezcano
2011-08-04 16:34 ` [ANNOUNCE] 3.0-rt6 : BUG at kernel/trmutex.c:724! Tim Sander
2011-08-04 16:37 ` Peter Zijlstra
2011-08-04 17:04 ` Tim Sander
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=20110729140307.GB2460@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.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