From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: [ANNOUNCE] 4.0.4-rt1
Date: Tue, 19 May 2015 23:39:23 +0200 [thread overview]
Message-ID: <20150519213923.GA26363@linutronix.de> (raw)
Dear RT folks!
I'm pleased to announce the v4.0.4-rt1 patch set.
Changes since v3.18.13-rt10
- Rebase to v4.0.
- David Hildenbrand's series of decouple of preempt_disable from
pagefault_disable is part of the series.
While doing the v4.0 I stumbled upon a few things. Therefore I plan to
reorder the -RT queue and merge patches where possible. Also I intend to
drop PREEMPT_RTB and PREEMPT_RT_BASE unless there is need for it…
Known issues:
- My AMD box throws a lot of "cpufreq_stat_notifier_trans: No
policy found" warnings after boot. It is gone after manually
setting the policy (to something else than reported).
- bcache is disabled.
- CPU hotplug works in general. Steven's test script however
deadlocks usually on the second invocation.
- xor / raid_pq
I had max latency jumping up to 67563us on one CPU while the next
lower max was 58us. I tracked it down to module's init code of
xor and raid_pq. Both disable preemption while measuring the
performance of the individual implementation.
The RT patch against 4.0.4 can be found here:
https://www.kernel.org/pub/linux/kernel/projects/rt/4.0/patch-4.0.4-rt1.patch.xz
The split quilt queue is available at:
https://www.kernel.org/pub/linux/kernel/projects/rt/4.0/patches-4.0.4-rt1.tar.xz
Sebastian
next reply other threads:[~2015-05-19 21:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 21:39 Sebastian Andrzej Siewior [this message]
2015-05-19 22:33 ` [ANNOUNCE] 4.0.4-rt1 Carsten Emde
2015-05-19 22:51 ` Pavel Vasilyev
2015-05-20 7:12 ` Sebastian Andrzej Siewior
2015-05-20 13:18 ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20 3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09 ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08 ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22 ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04 ` Mats Karrman
2015-06-11 13:14 ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12 7:22 ` Vinod Koul
2015-06-12 10:37 ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38 ` Steven Rostedt
2015-05-26 13:48 ` Clark Williams
2015-05-26 14:49 ` Mike Galbraith
2015-05-26 15:19 ` Steven Rostedt
2015-05-26 15:43 ` Clark Williams
2015-05-26 19:41 ` Fernando Lopez-Lezcano
2015-05-29 1:56 ` Fernando Lopez-Lezcano
2015-06-09 16:45 ` Fernando Lopez-Lezcano
2015-06-09 22:05 ` Pavel Vasilyev
2015-06-10 2:41 ` Mike Galbraith
2015-06-10 3:10 ` Fernando Lopez-Lezcano
2015-06-09 22:10 ` Pavel Vasilyev
2015-06-11 12:38 ` Sebastian Andrzej Siewior
2015-05-28 8:41 ` Joakim Hernberg
2015-06-11 12:34 ` Sebastian Andrzej Siewior
2015-05-27 9:44 ` Joakim Hernberg
2015-05-27 10:19 ` Jeremy Jongepier
2015-05-28 8:33 ` Joakim Hernberg
2015-05-27 15:50 ` Ralf Mardorf
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=20150519213923.GA26363@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.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).