linux-rt-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rt-devel@lists.linux.dev,
	Russell King <linux@armlinux.org.uk>,
	Xie Yuanbin <xieyuanbin1@huawei.com>
Subject: Re: [PATCH 3/5] ARM: Disable FAST_GUP on PREEMPT_RT if HIGHPTE is also enabled.
Date: Thu, 30 Oct 2025 16:24:25 +0100	[thread overview]
Message-ID: <20251030152425.TXa7Vocb@linutronix.de> (raw)
In-Reply-To: <324652fe-b5b8-45a6-9c57-096813e9092c@app.fastmail.com>

On 2025-10-30 16:15:42 [+0100], Arnd Bergmann wrote:
> On Wed, Oct 29, 2025, at 16:59, Sebastian Andrzej Siewior wrote:
> > --- a/arch/arm/Kconfig
> > +++ b/arch/arm/Kconfig
> > @@ -105,7 +105,7 @@ config ARM
> >  	select HAVE_DYNAMIC_FTRACE_WITH_REGS if HAVE_DYNAMIC_FTRACE
> >  	select HAVE_EFFICIENT_UNALIGNED_ACCESS if (CPU_V6 || CPU_V6K || CPU_V7) && MMU
> >  	select HAVE_EXIT_THREAD
> > -	select HAVE_GUP_FAST if ARM_LPAE
> > +	select HAVE_GUP_FAST if ARM_LPAE && !(PREEMPT_RT && HIGHPTE)
> >  	select HAVE_FUNCTION_ERROR_INJECTION
> >  	select HAVE_FUNCTION_GRAPH_TRACER
> >  	select HAVE_FUNCTION_GRAPH_FREGS
> 
> I would still prefer the version I posted previous at
> 
> https://lore.kernel.org/all/20241210160556.2341497-3-arnd@kernel.org/
> 
> disabling HIGHPTE when PREEMPT_RT is enabled.

I did remember that we shifted something I just wasn't sure what it was.
I will update for v2.

>      Arnd

Sebastian

  reply	other threads:[~2025-10-30 15:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 15:59 [PATCH 0/5] ARM: Remaining PREEMPT_RT bits Sebastian Andrzej Siewior
2025-10-29 15:59 ` [PATCH 1/5] ARM: mm: fault: Move harden_branch_predictor() before interrupts are enabled Sebastian Andrzej Siewior
2025-10-29 15:59 ` [PATCH 2/5] ARM: mm: fault: Enable interrupts before invoking __do_user_fault() Sebastian Andrzej Siewior
2025-10-29 15:59 ` [PATCH 3/5] ARM: Disable FAST_GUP on PREEMPT_RT if HIGHPTE is also enabled Sebastian Andrzej Siewior
2025-10-30 15:15   ` Arnd Bergmann
2025-10-30 15:24     ` Sebastian Andrzej Siewior [this message]
2025-10-29 15:59 ` [PATCH 4/5] ARM: Disable jump-label on PREEMPT_RT Sebastian Andrzej Siewior
2025-10-30  2:39   ` Xie Yuanbin
2025-10-30  7:23     ` Sebastian Andrzej Siewior
2025-10-30  7:45       ` Xie Yuanbin
2025-10-30  7:55         ` Sebastian Andrzej Siewior
2025-10-30  9:46           ` Steven Rostedt
2025-10-30  9:56             ` Sebastian Andrzej Siewior
2025-10-30 10:05               ` Steven Rostedt
2025-10-30 10:38           ` Russell King (Oracle)
2025-10-30 11:10             ` Sebastian Andrzej Siewior
2025-10-30 15:24   ` Arnd Bergmann
2025-10-30 15:28     ` Sebastian Andrzej Siewior
2025-10-29 15:59 ` [PATCH 5/5] ARM: Allow to enable RT Sebastian Andrzej Siewior
2025-10-30 15:18   ` Arnd Bergmann
2025-10-30 15:22     ` 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=20251030152425.TXa7Vocb@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=linux@armlinux.org.uk \
    --cc=xieyuanbin1@huawei.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;
as well as URLs for NNTP newsgroup(s).