From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/8] powerpc/signal: Convert to scoped user access
Date: Wed, 1 Jul 2026 10:58:52 +0200 [thread overview]
Message-ID: <63bef5b9-01e9-4272-a47e-e7ba4583a1a2@kernel.org> (raw)
In-Reply-To: <cover.1780389863.git.chleroy@kernel.org>
Le 02/06/2026 à 10:46, Christophe Leroy (CS GROUP) a écrit :
> This series converts powerpc architecture signal handling to scoped
> user access and enlarges some of the block accesses to minimise the
> number of times user access has to be opened and closed.
>
> As mentioned in individual patches, some bring real performance
> improvement.
>
> This series is built from previous series [1] which predates
> implementation of scoped user access.
>
> [1] https://lore.kernel.org/all/1718f38859d5366f82d5bef531f255cedf537b5d.1631861883.git.christophe.leroy@csgroup.eu/T/#t
Sashiko made relevant comments, I need to rework this series.
>
> Changes in v2:
> - Add a stub setup_tm_sigcontexts() for when CONFIG_PPC_TRANSACTIONAL_MEM is not set in patch 2
>
> Christophe Leroy (CS GROUP) (8):
> powerpc/signal32: Convert to scoped user access
> powerpc/signal64: Untangle setup_tm_sigcontexts() and
> user_access_begin()
> powerpc/signal64: Convert to scoped user access
> powerpc/signal64: Access function descriptor with scoped user access
> powerpc/signal: Include the new stack frame inside the user access
> block
> signal: Add unsafe_copy_siginfo_to_user()
> powerpc/uaccess: Add unsafe_clear_user()
> powerpc/signal: Use unsafe_copy_siginfo_to_user()
>
> arch/powerpc/include/asm/uaccess.h | 20 ++
> arch/powerpc/kernel/signal_32.c | 498 ++++++++++++++---------------
> arch/powerpc/kernel/signal_64.c | 138 ++++----
> include/linux/signal.h | 15 +
> include/linux/uaccess.h | 1 +
> kernel/signal.c | 5 -
> 6 files changed, 334 insertions(+), 343 deletions(-)
>
--
pw-bot: cr
prev parent reply other threads:[~2026-07-01 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:46 Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 1/8] powerpc/signal32: " Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 2/8] powerpc/signal64: Untangle setup_tm_sigcontexts() and user_access_begin() Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 3/8] powerpc/signal64: Convert to scoped user access Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 4/8] powerpc/signal64: Access function descriptor with " Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 5/8] powerpc/signal: Include the new stack frame inside the user access block Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 6/8] signal: Add unsafe_copy_siginfo_to_user() Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 7/8] powerpc/uaccess: Add unsafe_clear_user() Christophe Leroy (CS GROUP)
2026-06-02 8:46 ` [PATCH v2 8/8] powerpc/signal: Use unsafe_copy_siginfo_to_user() Christophe Leroy (CS GROUP)
2026-07-01 8:58 ` Christophe Leroy (CS GROUP) [this message]
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=63bef5b9-01e9-4272-a47e-e7ba4583a1a2@kernel.org \
--to=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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
Powered by JetHome