From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
npiggin@gmail.com, msuchanek@suse.de
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/2] powerpc/32: Implement C syscall entry/exit (complement)
Date: Tue, 9 Feb 2021 19:29:26 +0000 (UTC) [thread overview]
Message-ID: <cover.1612898425.git.christophe.leroy@csgroup.eu> (raw)
This series implements C syscall entry/exit for PPC32. It reuses
the work already done for PPC64.
This series is based on today's next-test (f538b53fd47a) where main patchs from v5 are merged in.
The first patch is important for performance.
v6:
- Forced scv param to 0 on syscall_exit_prepare(), and added is_not_scv bool.
- Reworked the last patch to avoid code duplication.
Christophe Leroy (2):
powerpc/syscall: Do not check unsupported scv vector on PPC32
powerpc/32: Handle bookE debugging in C in syscall entry/exit
arch/powerpc/include/asm/interrupt.h | 12 +++++++
arch/powerpc/include/asm/ptrace.h | 5 +++
arch/powerpc/include/asm/reg_booke.h | 3 ++
arch/powerpc/kernel/entry_32.S | 7 ----
arch/powerpc/kernel/head_32.h | 15 ---------
arch/powerpc/kernel/head_booke.h | 19 -----------
arch/powerpc/kernel/interrupt.c | 50 ++++++++++++++++++----------
7 files changed, 52 insertions(+), 59 deletions(-)
--
2.25.0
next reply other threads:[~2021-02-09 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 19:29 Christophe Leroy [this message]
2021-02-09 19:29 ` [PATCH v6 1/2] powerpc/syscall: Do not check unsupported scv vector on PPC32 Christophe Leroy
2021-02-09 19:29 ` [PATCH v6 2/2] powerpc/32: Handle bookE debugging in C in syscall entry/exit Christophe Leroy
2021-02-10 8:44 ` [PATCH v6 3/2] powerpc/syscall: Avoid storing 'current' in another pointer Christophe Leroy
2021-02-12 0:19 ` [PATCH v6 0/2] powerpc/32: Implement C syscall entry/exit (complement) Michael Ellerman
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=cover.1612898425.git.christophe.leroy@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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).