public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: RT-Users <linux-rt-users@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	"jcaceres@ccrma.Stanford.EDU" <jcaceres@ccrma.Stanford.EDU>,
	Carsten Emde <Carsten.Emde@osadl.org>
Subject: v2.6.21.5-rt19
Date: Wed, 04 Jul 2007 22:49:15 +0200	[thread overview]
Message-ID: <1183582155.3291.160.camel@chaos> (raw)

I'm pleased to announce the v2.6.21.5-rt19 kernel on behalf of Ingo.

It can be downloaded from the usual place:
 
     http://people.redhat.com/mingo/realtime-preempt/
  
More info about the -rt patch set can be found in the RT wiki:
   
     http://rt.wiki.kernel.org

Changes since 2.6.21.5-rt18:

- Fixed a nasty and hard to track down slowness / boot problem on SMP
machines with CONFIG_NOHZ enabled. The problem was caused by the timer
wheel base lock held during the get_next_timer_interrupt() call in the
idle path, which eventually led to a bogus PI boosting of the idle task
and in consequence a stale wrong scheduler selection for the affected
idle task.

Kudos to Carsten Emde, who patiently and meticulously isolated the
problem and provided the traces, which allowed to identify the root
cause.

Problem solution: Prevent idle task boosting

- back port of the ntp / clock_was_set fix

- integration of the processor_idle fix from Venki Pallipadi, which
resolves boot issues on some platforms

- ep93xx clock events fix from Manfred Gruber


To build a 2.6.21.5-rt19 tree, the following patches should be applied:
  
    http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.5.tar.bz2
    http://people.redhat.com/mingo/realtime-preempt/patch-2.6.21.5-rt19

Thanks,

	tglx



             reply	other threads:[~2007-07-04 20:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 20:49 Thomas Gleixner [this message]
2007-07-06 14:10 ` v2.6.21.5-rt19 Rui Nuno Capela
2007-07-06 21:49   ` v2.6.21.5-rt19 Fernando Lopez-Lezcano
2007-07-07  9:15     ` v2.6.21.5-rt19 Ingo Molnar
2007-07-07  9:24     ` v2.6.21.5-rt19 Ingo Molnar
2007-07-08 22:36       ` v2.6.21.5-rt19 Fernando Lopez-Lezcano
2007-07-08 22:50         ` v2.6.21.5-rt19 Fernando Lopez-Lezcano
2007-07-08 23:42         ` v2.6.21.5-rt19 Gabriel C
2007-07-09  3:53           ` v2.6.21.5-rt19 Fernando Pablo Lopez-Lezcano
2007-07-09  5:08             ` v2.6.21.5-rt19 (sched_getaffinity?) Fernando Lopez-Lezcano
2007-07-17 19:32               ` Ingo Molnar
2007-07-17 19:47                 ` Fernando Lopez-Lezcano
2007-07-17 19:56                 ` Fernando Lopez-Lezcano
2007-07-17 20:12                   ` Ingo Molnar
2007-07-17 21:41                     ` Fernando Lopez-Lezcano
2007-07-17 23:51                     ` Fernando Lopez-Lezcano
2007-07-18  7:18                       ` Ingo Molnar
2007-07-18 13:21                         ` Paul E. McKenney
2007-07-18 18:02                         ` Fernando Lopez-Lezcano

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=1183582155.3291.160.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=Carsten.Emde@osadl.org \
    --cc=jcaceres@ccrma.Stanford.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.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