From: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
To: Daniel Wagner <wagi@monom.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
pavel@nabladev.com, nobuhiro.iwamatsu.x90@mail.toshiba,
stable-rt@vger.kernel.org, cip-dev@lists.cip-project.org
Subject: Re: v6.12-rt arm updates
Date: Fri, 17 Jul 2026 15:46:24 +0200 [thread overview]
Message-ID: <20260717134624._f9g97lg@linutronix.de> (raw)
In-Reply-To: <8a0f6ad1-0df7-4707-bcc4-83603cada945@monom.org>
On 2026-07-17 13:30:15 [+0000], Daniel Wagner wrote:
> Hi,
Hi,
> I am about to update v6.12-rt and the arm section needs some updates.
> Here is what I am going to do. Please let me know if there is something
> wrong.
not sure how to read this below, I try my best.
> Thanks,
> Daniel
>
> ###########################################################################
> # ARM
> ###########################################################################
> # https://lore.kernel.org/all/cover.1777964226.git.jan.kiszka@siemens.com/
>
> # v6.12-stable material relevant for RT but no patches to drop from
> # rt queue:
> # 47c5d569d39d ("ARM: group is_permission_fault() with
> is_translation_fault()")
> # d5e8be7bea8d ("ARM: allow __do_kernel_fault() to report execution of
> memory faults")
> # 25ae6a5c473b ("ARM: fix hash_name() fault")
> # fed889edca79 ("ARM: fix branch predictor hardening")
Those few should have entered via -stable.
> # landed in v6.12-stable, thus drop those
> # (commit ids from v6.12-stable):
> # 0001-arm-Disable-jump-label-on-PREEMPT_RT.patch
> # 256d97d3587b ("ARM: 9459/1: Disable jump-label on PREEMPT_RT")
>
> # arm-Disable-FAST_GUP-on-PREEMPT_RT-if-HIGHPTE-is-als.patch
> # 1b645cd729ef ("ARM: 9461/1: Disable HIGHPTE on PREEMPT_RT kernels")
>
> # Commits in upstream but not in v6.12-stable
> ARM__enable_irq_in_translation_section_permission_fault_handlers.patch
> # 59e4f3b45b96 ("ARM: ensure interrupts are enabled in __do_user_fault()")
You should be able to drop a few of those and replace them with what I
have in v6.18
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/commit/?h=linux-6.18.y-rt-patches&id=73c8e8d7a75fcc8b9026385e64990f3d5ec8a40d
> 0001-ARM-vfp-Provide-vfp_state_hold-for-VFP-locking.patch
> 0002-ARM-vfp-Use-vfp_state_hold-in-vfp_sync_hwstate.patch
> 0003-ARM-vfp-Use-vfp_state_hold-in-vfp_support_entry.patch
> 0004-ARM-vfp-Move-sending-signals-outside-of-vfp_state_ho.patch
> # f26bdbe1fa9f ("ARM: 9423/1: vfp: Provide vfp_state_hold() for VFP
> locking.")
> # b54cdbad4a39 ("ARM: 9424/1: vfp: Use vfp_state_hold() in
> vfp_sync_hwstate().")
> # 27035c23bad5 ("ARM: 9425/1: vfp: Use vfp_state_hold() in
> vfp_support_entry().")
> # c0b5195bad63 ("ARM: 9426/1: vfp: Move sending signals outside of
> vfp_state_hold()ed section.")
And this needs to stay
> ARM__Allow_to_enable_RT.patch
> # c6e61c06d606 ("ARM: 9463/1: Allow to enable RT")
>
Sebastian
next prev parent reply other threads:[~2026-07-20 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:30 v6.12-rt arm updates Daniel Wagner
2026-07-17 13:41 ` Daniel Wagner
2026-07-17 13:46 ` bigeasy [this message]
2026-07-17 13:54 ` Daniel Wagner
2026-07-17 14:03 ` bigeasy
2026-07-17 14:17 ` Daniel Wagner
2026-07-17 14:22 ` bigeasy
2026-07-21 13:06 ` Daniel Wagner
2026-07-21 13:10 ` bigeasy
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=20260717134624._f9g97lg@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
--cc=stable-rt@vger.kernel.org \
--cc=wagi@monom.org \
/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