From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.0.19-rt11
Date: Fri, 31 May 2019 21:31:25 +0200 [thread overview]
Message-ID: <20190531193124.ao2skirq6rkdrgyn@linutronix.de> (raw)
In-Reply-To: <20190529212638.g3gkor3n7xui5fhk@linutronix.de>
On 2019-05-29 23:26:38 [+0200], To Thomas Gleixner wrote:
> Dear RT folks!
>
> I'm pleased to announce the v5.0.19-rt11 patch set.
>
> Changes since v5.0.19-rt10:
>
> - Ignore a warning from lockdep when lockdep is disabled for different
> lock types.
>
> - Make the cpuidle an imx6 raw_spinlock_t.
>
> - Add a proper depends in Kconfig for Atmel's tclib based clocksource.
> Otherwise the allmodconfig on !ATMEL fails.
>
> - Revert the removal of TIMER_IRQSAFE in i915 because it is required.
>
> - Rework the softirq code.
> The basic idea is to have local-lock within local_bh_disable() which is
> used for synchronisation similar to mainline. With this synchronisation
> we can't have two softirqs processed in parallel on the same CPU. This
> allows to remove the extra synchronisation we had.
>
> - Rework the workqueue code.
> The worker_pool.lock is made to raw_spinlock_t. With this change we can
> schedule workitems from preempt-disable sections and sections with
> disabled interrupts. This change allows to remove all kthread_.*
> workarounds we used to have.
>
> Known issues
> - A warning triggered in "rcu_note_context_switch" originated from
> SyS_timer_gettime(). The issue was always there, it is now
> visible. Reported by Grygorii Strashko and Daniel Wagner.
>
> - rcutorture is currently broken on -RT. Reported by Juri Lelli.
>
> The delta patch against v5.0.19-rt10 is appended below and can be found here:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.0/incr/patch-5.0.19-rt10-rt11.patch.xz
>
> You can get this release via the git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v5.0.19-rt11
>
> The RT patch against v5.0.19 can be found here:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.0/older/patch-5.0.19-rt11.patch.xz
>
> The split quilt queue is available at:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.0/older/patches-5.0.19-rt11.tar.xz
just noticed that this never made it to the due to large inline diff.
The diff can be looked up at
https://git.kernel.org/rt/linux-rt-devel/d/v5.0.19-rt11/v5.0.19-rt10
Sebastian
parent reply other threads:[~2019-05-31 19:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190529212638.g3gkor3n7xui5fhk@linutronix.de>]
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=20190531193124.ao2skirq6rkdrgyn@linutronix.de \
--to=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;
as well as URLs for NNTP newsgroup(s).