CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Siewior <bigeasy@linutronix.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: cip-dev@lists.cip-project.org, pavel@nabladev.com,
	nobuhiro.iwamatsu.x90@mail.toshiba, Bryan Brattlof <bb@ti.com>,
	Daniel Wagner <daniel.wagner@monom.org>
Subject: Re: [RFC][PATCH 6.12.y-cip 00/12] Backport PREEMPT-RT support for ARM 32-bit
Date: Tue, 12 May 2026 08:37:03 +0200	[thread overview]
Message-ID: <20260512063703.aRyfXa5N@linutronix.de> (raw)
In-Reply-To: <f3936f46-549c-425a-bd58-c60705be5c21@siemens.com>

On 2026-05-11 18:26:18 [+0200], Jan Kiszka wrote:
> > | ARM: ensure interrupts are enabled in __do_user_fault()
> > | ARM: 9459/1: Disable jump-label on PREEMPT_RT
> > | ARM: 9463/1: Allow to enable RT
> > This would go to stable-rt. This does not fix anything !RT as far as I
> > can tell.
> > 
> 
> Ok, then they would be equivalently relevant for 6.12-cip

Once it goes via stable, I throw it at the stable pile to ease their
rebase on top stable.

> > The four patches for stable have been sent.
> > 
> 
> 12-7 = 5. One is "Allow to enable RT", obviously needed in stable-rt and
> -cip then as well. What about the other 4? Not needed in a backport?

I dropped from your queue:

| ARM: move vmalloc() lazy-page table population
| ARM: move is_permission_fault() and is_translation_fault() to fault.h
| ARM: use BIT() and GENMASK() for fault status register fields
| ARM: move FSR fault status definitions before fsr_fs()
| ARM: provide individual is_translation_fault() and is_permission_fault()

as far as I can tell, it is just shuffling code around. Not strictly
needed for the backport. The "grouping" patch that I sent stable@ is
also moving code around but the following "fix" needs the forward
declaration so it goes in as a requirement.
I don't see the need for these.

> Thanks so far already!
> Jan

Sebastian


  reply	other threads:[~2026-05-12  8:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  6:56 [RFC][PATCH 6.12.y-cip 00/12] Backport PREEMPT-RT support for ARM 32-bit Jan Kiszka
2026-05-05  6:56 ` [RFC][PATCH 6.12.y-cip 01/12] ARM: group is_permission_fault() with is_translation_fault() Jan Kiszka
2026-05-05  6:56 ` [RFC][PATCH 6.12.y-cip 02/12] ARM: allow __do_kernel_fault() to report execution of memory faults Jan Kiszka
2026-05-05  6:56 ` [RFC][PATCH 6.12.y-cip 03/12] ARM: fix hash_name() fault Jan Kiszka
2026-05-05  6:56 ` [RFC][PATCH 6.12.y-cip 04/12] ARM: fix branch predictor hardening Jan Kiszka
2026-05-05  6:56 ` [RFC][PATCH 6.12.y-cip 05/12] ARM: 9459/1: Disable jump-label on PREEMPT_RT Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 06/12] ARM: ensure interrupts are enabled in __do_user_fault() Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 07/12] ARM: move vmalloc() lazy-page table population Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 08/12] ARM: move is_permission_fault() and is_translation_fault() to fault.h Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 09/12] ARM: use BIT() and GENMASK() for fault status register fields Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 10/12] ARM: move FSR fault status definitions before fsr_fs() Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 11/12] ARM: provide individual is_translation_fault() and is_permission_fault() Jan Kiszka
2026-05-05  6:57 ` [RFC][PATCH 6.12.y-cip 12/12] ARM: 9463/1: Allow to enable RT Jan Kiszka
2026-05-05  7:02 ` [RFC][PATCH 6.12.y-cip 00/12] Backport PREEMPT-RT support for ARM 32-bit Jan Kiszka
2026-05-11 13:57   ` Sebastian Siewior
2026-05-11 16:26     ` Jan Kiszka
2026-05-12  6:37       ` Sebastian Siewior [this message]
2026-05-12  8:11 ` Pavel Machek
2026-05-12  9:42   ` Jan Kiszka

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=20260512063703.aRyfXa5N@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bb@ti.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.wagner@monom.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=pavel@nabladev.com \
    /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