From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] 4.8-rc5-rt1 beta
Date: Sun, 2 Oct 2016 19:35:15 -0400 [thread overview]
Message-ID: <20161002233515.GA18997@windriver.com> (raw)
In-Reply-To: <20160906182508.GB9950@windriver.com>
[[ANNOUNCE] 4.8-rc5-rt1 beta] On 06/09/2016 (Tue 14:25) Paul Gortmaker wrote:
> This is a carry forward of the -rt patches off v4.6.7-rt11 through
> mainline commits of v4.7 and up to the current v4.8-rc5.
>
> https://git.kernel.org/cgit/linux/kernel/git/paulg/4.8-rt-patches.git
>
[...]
>
> Patch conflicts/issues of interest 4.7 --> 4.8
> ----------------------------------------------
>
-mainline changed the qdisc from a simple bit to a seqcount; this causes
a splat from migrate_enable, but I didn't initially see that since the
sanity check relies on SCHED_DEBUG=y. This causes the -rt patch that
faked out the lock status to splat; further details are at kernel.org:
https://goo.gl/0fdRKR
No point in anyone else having to redo the root cause research on this a
second time; I've updated the above repo for this and for some other mm
fallout from 4.8-rc7 in memcontrol.c so that the patches will apply for
what inevitably becomes v4.8 final in a couple hours.
That said, my original comments still apply -- this remains as a resource
for developers who track the -rt progress, and how mainline will impact
it. The release of 4.8 in mainline does not somehow change this repo
into a stable/supported -rt release by osmosis. If you don't regularly
manually apply and test patches, including resolving sleeping while
atomic kernel backtrace dumps, you probably should not be using this.
Paul.
prev parent reply other threads:[~2016-10-02 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:25 [ANNOUNCE] 4.8-rc5-rt1 beta Paul Gortmaker
2016-09-08 5:47 ` Mike Galbraith
2016-09-17 20:45 ` Paul Gortmaker
2016-10-02 23:35 ` Paul Gortmaker [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=20161002233515.GA18997@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bigeasy@linutronix.de \
--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