From: Thomas Gleixner <tglx@linutronix.de>
To: Valentin Schneider <vschneid@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Mike Galbraith <efault@gmx.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Mark Brown <broonie@kernel.org>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Petr Tesarik <ptesarik@suse.com>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Juri Lelli <juri.lelli@redhat.com>, Phil Auld <pauld@redhat.com>
Subject: Re: [PATCH 1/1] arm64: enable PREEMPT_LAZY
Date: Wed, 05 Mar 2025 13:48:30 +0100 [thread overview]
Message-ID: <87cyev63tt.ffs@tglx> (raw)
In-Reply-To: <20250305104925.189198-2-vschneid@redhat.com>
On Wed, Mar 05 2025 at 11:49, Valentin Schneider wrote:
> From: Mark Rutland <mark.rutland@arm.com>
>
> For an architecture to enable CONFIG_ARCH_HAS_RESCHED_LAZY, two things are
> required:
> 1) Adding a TIF_NEED_RESCHED_LAZY flag definition
> 2) Checking for TIF_NEED_RESCHED_LAZY in the appropriate locations
>
> 2) is handled in a generic manner by CONFIG_GENERIC_ENTRY, which isn't
> (yet) implemented for arm64. However, outside of core scheduler code,
> TIF_NEED_RESCHED_LAZY only needs to be checked on a kernel exit, meaning:
> o return/entry to userspace.
> o return/entry to guest.
>
> The return/entry to a guest is all handled by xfer_to_guest_mode_handle_work()
> which already does the right thing, so it can be left as-is.
>
> arm64 doesn't use common entry's exit_to_user_mode_prepare(), so update its
> return to user path to check for TIF_NEED_RESCHED_LAZY and call into
> schedule() accordingly.
>
> Link: https://lore.kernel.org/linux-rt-users/20241216190451.1c61977c@mordecai.tesarici.cz/
> Link: https://lore.kernel.org/all/xhsmh4j0fl0p3.mognet@vschneid-thinkpadt14sgen2i.remote.csb/
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> [testdrive, _TIF_WORK_MASK fixlet and changelog.]
> Signed-off-by: Mike Galbraith <efault@gmx.de>
> [Another round of testing; changelog faff]
> Signed-off-by: Valentin Schneider <vschneid@redhat.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2025-03-05 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:49 [PATCH 0/1] arm64: enable PREEMPT_LAZY Valentin Schneider
2025-03-05 10:49 ` [PATCH 1/1] " Valentin Schneider
2025-03-05 11:06 ` Sebastian Andrzej Siewior
2025-03-05 12:15 ` Mark Rutland
2025-03-06 12:23 ` Petr Tesarik
2025-03-31 9:07 ` Sebastian Andrzej Siewior
2025-04-29 12:45 ` Will Deacon
2025-03-05 12:48 ` Thomas Gleixner [this message]
2025-05-07 22:51 ` Paul E. McKenney
2025-03-05 14:03 ` [PATCH 0/1] " Phil Auld
2025-04-29 20:27 ` Will Deacon
2025-04-30 8:38 ` Petr Tesarik
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=87cyev63tt.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=efault@gmx.de \
--cc=juri.lelli@redhat.com \
--cc=kristina.martsenko@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=pauld@redhat.com \
--cc=pcc@google.com \
--cc=ptesarik@suse.com \
--cc=ruanjinjie@huawei.com \
--cc=thiago.bauermann@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).