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.6.17-rt10
Date: Tue, 16 Jun 2020 18:47:57 +0200 [thread overview]
Message-ID: <20200616164757.o6qlarnluib2szl5@linutronix.de> (raw)
In-Reply-To: <20200616124502.vfmbsec3avnbhupz@linutronix.de>
On 2020-06-16 14:45:03 [+0200], To Thomas Gleixner wrote:
> Dear RT folks!
>
> I'm pleased to announce the v5.6.17-rt10 patch set.
>
> Changes since v5.6.17-rt9:
>
> - Add the seqcount series by Ahmed S. Darwish.
> The series annotates the lock protecting the struct seqcount against
> multiple writer. In RT the lock annotation can be utilized to block
> on in case the writer is active. This is the same technique that is
> used now but we can avoid replacing the seqcount with a seqlock and
> have code that is closer to mainline.
>
> As part of the integration I dropped seqcount replacements which
> are no longer needed, like in NFS or vfs.
>
> - Added down_read_non_owner() for RT. There is no owner tracking since
> we allow multiple reader locking on struct rw_semaphore. This
> removes on patch from the NFS subsystem and allows to enable bcache.
>
> - Drop the lock raw_spinlock_t from struct hlist_bl_head. The struct
> hlist_bl_head uses bit_spin_lock() for locking so we are still
> spinning.
>
> Known issues
> - It has been pointed out that due to changes to the printk code the
> internal buffer representation changed. This is only an issue if tools
> like `crash' are used to extract the printk buffer from a kernel memory
> image.
>
> The delta patch against v5.6.17-rt9 is appended below and can be found here:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.6/incr/patch-5.6.17-rt9-rt10.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.6.17-rt10
>
> The RT patch against v5.6.17 can be found here:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.6/older/patch-5.6.17-rt10.patch.xz
>
> The split quilt queue is available at:
>
> https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.6/older/patches-5.6.17-rt10.tar.xz
Again without the delta diff since the email was too huge. It can be
still look on at
https://git.kernel.org/rt/linux-rt-devel/d/v5.6.17-rt10/v5.6.17-rt9
Sebastian
parent reply other threads:[~2020-06-16 16:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200616124502.vfmbsec3avnbhupz@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=20200616164757.o6qlarnluib2szl5@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).