From: Thomas Gleixner <tglx@linutronix.de>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH v5 4/4] entry: Inline syscall_exit_to_user_mode()
Date: Sun, 09 Mar 2025 09:23:20 +0100 [thread overview]
Message-ID: <87jz8y3953.ffs@tglx> (raw)
In-Reply-To: <Z8zb-L8bFMh_YHxO@ghost>
On Sat, Mar 08 2025 at 16:08, Charlie Jenkins wrote:
> On Sat, Mar 08, 2025 at 01:37:30PM +0100, Thomas Gleixner wrote:
>> On Wed, Mar 05 2025 at 16:43, Charlie Jenkins wrote:
>> > Architectures using the generic entry code can be optimized by having
>> > syscall_exit_to_user_mode inlined.
>>
>> That's a pretty handwavy claim. What's the actual benefit in numbers?
>
> I put the numbers in the cover letter! Here is the data I gathered:
They should be in the change log as the cover letter is not part of what
ends up in git.
next prev parent reply other threads:[~2025-03-09 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 0:43 [PATCH v5 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode() Charlie Jenkins
2025-03-06 0:43 ` [PATCH v5 1/4] riscv: entry: Convert ret_from_fork() to C Charlie Jenkins
2025-03-06 0:43 ` [PATCH v5 2/4] riscv: entry: Split ret_from_fork() into user and kernel Charlie Jenkins
2025-03-10 9:51 ` Alexandre Ghiti
2025-03-06 0:43 ` [PATCH v5 3/4] LoongArch: entry: Migrate ret_from_fork() to C Charlie Jenkins
2025-03-06 0:43 ` [PATCH v5 4/4] entry: Inline syscall_exit_to_user_mode() Charlie Jenkins
2025-03-08 12:37 ` Thomas Gleixner
2025-03-09 0:08 ` Charlie Jenkins
2025-03-09 8:23 ` Thomas Gleixner [this message]
2025-03-10 4:34 ` Charlie Jenkins
2025-03-10 9:58 ` Alexandre Ghiti
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=87jz8y3953.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexghiti@rivosinc.com \
--cc=charlie@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 \
/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