From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Esben Nielsen <simlo@phys.au.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: 2.6.15-rt17
Date: Tue, 21 Feb 2006 16:55:48 +0100 [thread overview]
Message-ID: <20060221155548.GA30146@elte.hu> (raw)
i have released the 2.6.15-rt17 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
lots of changes all across the map. There are several bigger changes:
the biggest change is the new PI code from Esben Nielsen, Thomas
Gleixner and Steven Rostedt. This big rework simplifies and streamlines
the PI code, and fixes a couple of bugs and races:
- only the top priority waiter on a lock is enqueued into the pi_list
of the task which holds the lock. No more pi list walking in the
boost case.
- simpler locking rules
- fast Atomic acquire for the non contended case and atomic release
for non waiter case is fully functional now
- use task_t references instead of thread_info pointers
- BKL handling for semaphore style locks changed so that BKL is
dropped before the scheduler is entered and reaquired in the return
path. This solves a possible deadlock situation in the BKL reacquire
path of the scheduler.
another change is the reworking of the SLAB code: it now closely matches
the upstream SLAB code, and it should now work on NUMA systems too
(untested though).
the tasklet code was reworked too to be PREEMPT_RT friendly: the new PI
code unearthed a fundamental livelock scenario with PREEMPT_RT, and the
fix was to rework the tasklet code to get rid of the 'retrigger
softirqs' approach.
other changes: various hrtimers fixes, latency tracer enhancements - and
more. (Robust-futexes are not expected to work in this release.)
please report any new breakages, and re-report any old breakages as
well.
to build a 2.6.15-rt17 tree, the following patches should be applied:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2
http://redhat.com/~mingo/realtime-preempt/patch-2.6.15-rt17
Ingo
next reply other threads:[~2006-02-21 15:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 15:55 Ingo Molnar [this message]
2006-02-21 16:11 ` 2.6.15-rt17 K.R. Foley
2006-02-21 16:21 ` 2.6.15-rt17 K.R. Foley
2006-02-22 7:51 ` 2.6.15-rt17 Ingo Molnar
2006-02-21 17:16 ` 2.6.15-rt17 Michal Piotrowski
2006-02-21 18:53 ` 2.6.15-rt17 Michal Piotrowski
2006-02-21 20:37 ` 2.6.15-rt17 Thomas Gleixner
2006-02-21 21:15 ` 2.6.15-rt17 Michal Piotrowski
2006-02-22 12:22 ` 2.6.15-rt17 Steven Rostedt
2006-02-22 13:47 ` 2.6.15-rt17 Michal Piotrowski
2006-02-24 6:38 ` 2.6.15-rt17 Ingo Molnar
2006-02-24 7:09 ` 2.6.15-rt17 Steven Rostedt
2006-02-21 17:23 ` 2.6.15-rt17 Timothy R. Chavez
2006-02-21 18:24 ` 2.6.15-rt17 Daniel Walker
2006-02-21 18:46 ` 2.6.15-rt17 Thomas Gleixner
2006-02-22 16:50 ` 2.6.15-rt17 Esben Nielsen
2006-02-22 23:17 ` 2.6.15-rt17 Thomas Gleixner
2006-02-25 17:11 ` 2.6.15-rt17 Esben Nielsen
2006-02-25 17:32 ` 2.6.15-rt17 Steven Rostedt
2006-02-25 21:29 ` 2.6.15-rt17 Esben Nielsen
2006-02-25 22:25 ` 2.6.15-rt17 Esben Nielsen
2006-02-26 15:14 ` 2.6.15-rt17 Steven Rostedt
2006-02-26 22:38 ` 2.6.15-rt17 Esben Nielsen
2006-02-27 7:15 ` 2.6.15-rt17 Steven Rostedt
2006-02-23 13:49 ` 2.6.15-rt17 Bill Huey
2006-02-23 13:53 ` 2.6.15-rt17 Ingo Molnar
2006-02-23 14:05 ` 2.6.15-rt17 Bill Huey
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 19:21 2.6.15-rt17 Karsten Wiese
2006-02-28 19:43 ` 2.6.15-rt17 Ingo Molnar
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=20060221155548.GA30146@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=simlo@phys.au.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.