From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>, linux-rt-devel@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Maarten Lankhorst <dev@lankhorst.se>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: [ANNOUNCE] v7.3-rc4-rt1
Date: Tue, 22 Sep 2026 16:41:52 +0200 [thread overview]
Message-ID: <20260922144152.x2J3_tNz@linutronix.de> (raw)
Dear RT folks!
I'm pleased to announce the v7.3-rc4-rt1 patch set.
Changes since v7.2-rt5:
- Rebase to v7.3-rc4
The printk related changes are all gone. What is left in the queue is
PowerPC, i915 and a sysfs file:
- PowerPC
Some progress has been made. What is left is a pseries related MMU
change, a patch dropping KVM_MPIC (which is e500 only) and a stack
protector related workaround.
The stack protector workaround might work with a different fix since
only arch/powerpc is using boot_init_stack_canary().
- i915
The patches in the queue are different compared to what is worked on.
Both sides seem to be stuck. The XE driver seemed to be an alternative
on platforms which are supported. Now that I test it has the same
vblank issues as the i915.
- sysfs file, /sys/kernel/realtime
This file has been around since forever. It was used to "easily"
detect if the PREEMPT_RT patch has been applied and the required
Kconfig symbol has been enabled.
There has been a discussion if this file should be upstreamed, if it
should remain at the same location or if it should become a folder
with features.
Any change here implies that users need to update their scripts. Even
if the file is present in !PREEMPT_RT kernels and returns 0 (as the
file was created with the patch queue applied but CONFIG_PREEMPT_RT nt
selected).
Given that this never part of an upstream kernel, it is probably best to
no include it. The uname(2) interface provides the same information.
I am considering not updating the queue anymore given how much has been
accomplished.
Known issues
- Yoann Congal reported a bit spinlock in dm_exception_table_lock().
https://lore.kernel.org/all/Z8GTjqgDe_5EkE3t@P-ASN-ECS-830T8C3.local
You can get this release via the git tree at:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v7.3-rc4-rt1
The RT patch against v7.3-rc4 can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/7.3/older/patch-7.3-rc4-rt1.patch.xz
The split quilt queue is available at:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/7.3/older/patches-7.3-rc4-rt1.tar.xz
Sebastian
reply other threads:[~2026-09-22 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260922144152.x2J3_tNz@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=dev@lankhorst.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--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
all inboxes | Powered by JetHome®