From: Charlie Jenkins <charlie@rivosinc.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev,
Charlie Jenkins <charlie@rivosinc.com>
Subject: [PATCH 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode()
Date: Wed, 22 Jan 2025 14:56:19 -0800 [thread overview]
Message-ID: <20250122-riscv_optimize_entry-v1-0-4ee95559cfd0@rivosinc.com> (raw)
Similar to commit 221a164035fd ("entry: Move
syscall_enter_from_user_mode() to header file"), move
syscall_exit_to_user_mode() to the header file as well.
Testing was done with the byte-unixbench [1] syscall benchmark (which
calls getpid) and QEMU. On riscv I measured a 7.09246% improvement, on
x86 a 2.98843% improvement, on loongarch a 6.07954% improvement, and on
s390 a 11.1328% improvement.
Since this is on QEMU, I know these numbers are not perfect, but they
show a trend of general improvement across all architectures that use
the generic entry code.
[1] https://github.com/kdlucas/byte-unixbench
Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
---
Charlie Jenkins (4):
riscv: entry: Convert ret_from_fork() to C
riscv: entry: Split ret_from_fork() into user and kernel
loongarch: entry: Migrate ret_from_fork() to C
entry: Inline syscall_exit_to_user_mode()
arch/loongarch/include/asm/switch_to.h | 8 ++++++
arch/loongarch/kernel/entry.S | 22 +++++++--------
arch/loongarch/kernel/process.c | 36 ++++++++++++++++++++----
arch/riscv/include/asm/asm-prototypes.h | 2 ++
arch/riscv/kernel/entry.S | 20 ++++++++------
arch/riscv/kernel/process.c | 21 ++++++++++++--
include/linux/entry-common.h | 43 +++++++++++++++++++++++++++--
kernel/entry/common.c | 49 +--------------------------------
8 files changed, 122 insertions(+), 79 deletions(-)
---
base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
change-id: 20240402-riscv_optimize_entry-583843420325
--
- Charlie
next reply other threads:[~2025-01-22 22:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 22:56 Charlie Jenkins [this message]
2025-01-22 22:56 ` [PATCH 1/4] riscv: entry: Convert ret_from_fork() to C Charlie Jenkins
2025-01-24 7:09 ` Alexandre Ghiti
2025-01-24 7:56 ` Charlie Jenkins
2025-01-25 23:30 ` Maciej W. Rozycki
2025-01-26 19:51 ` Charlie Jenkins
2025-01-27 20:20 ` Maciej W. Rozycki
2025-01-27 20:55 ` Charlie Jenkins
2025-01-22 22:56 ` [PATCH 2/4] riscv: entry: Split ret_from_fork() into user and kernel Charlie Jenkins
2025-01-22 22:56 ` [PATCH 3/4] loongarch: entry: Migrate ret_from_fork() to C Charlie Jenkins
2025-01-23 17:12 ` kernel test robot
2025-01-22 22:56 ` [PATCH 4/4] entry: Inline syscall_exit_to_user_mode() Charlie Jenkins
2025-01-23 17:12 ` kernel test robot
2025-01-23 17:34 ` kernel test robot
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=20250122-riscv_optimize_entry-v1-0-4ee95559cfd0@rivosinc.com \
--to=charlie@rivosinc.com \
--cc=alexghiti@rivosinc.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=luto@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®