From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rt-devel@lists.linux.dev, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
"Yadi.hu" <yadi.hu@windriver.com>
Subject: Re: [PATCH v5 1/2] ARM: mm: fault: Enable interrupts before invoking __do_user_fault()
Date: Thu, 26 Feb 2026 14:14:59 +0100 [thread overview]
Message-ID: <20260226131459.8lBz2Cbs@linutronix.de> (raw)
In-Reply-To: <aaA8uR3_o55uuevl@shell.armlinux.org.uk>
On 2026-02-26 12:29:45 [+0000], Russell King (Oracle) wrote:
> Sorry, I've been swamped with stmmac for ages, which has become a
> millstone.
>
> I need to push out these patches:
>
> ARM: provide individual is_translation_fault() and is_permission_fault()
> ARM: move FSR fault status definitions before fsr_fs()
> ARM: use BIT() and GENMASK() for fault status register fields
> ARM: move is_permission_fault() and is_translation_fault() to fault.h
> ARM: move vmalloc() lazy-page table population
> ARM: ensure interrupts are enabled in __do_user_fault()
>
> which will address some of your issues, and clean up the fault handling
> code. These patches all date from 5th December. :/
Okay. Thank you. Please let me know once you pushed them where I can
reach them. Then maybe we can reduce this to just 2/2 ;)
Sebastian
next prev parent reply other threads:[~2026-02-26 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 11:17 [PATCH v5 0/2] ARM: Remaining PREEMPT_RT bits Sebastian Andrzej Siewior
2026-02-26 11:17 ` [PATCH v5 1/2] ARM: mm: fault: Enable interrupts before invoking __do_user_fault() Sebastian Andrzej Siewior
2026-02-26 12:29 ` Russell King (Oracle)
2026-02-26 13:14 ` Sebastian Andrzej Siewior [this message]
2026-02-26 11:17 ` [PATCH v5 2/2] ARM: Allow to enable RT Sebastian Andrzej Siewior
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=20260226131459.8lBz2Cbs@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=yadi.hu@windriver.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