From: Qingfang Deng <dqfext@gmail.com>
To: alexghiti@rivosinc.com
Cc: aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, samuel.holland@sifive.com
Subject: Re: [PATCH] riscv: Improve sbi_ecall() code generation by reordering arguments
Date: Sat, 23 Mar 2024 14:26:25 +0800 [thread overview]
Message-ID: <20240323062625.2488-1-dqfext@gmail.com> (raw)
In-Reply-To: <20240322112629.68170-1-alexghiti@rivosinc.com>
Hi Alexandre,
You can simply make sbi_ecall `__always_inline`, so the C function call
overhead can be fully avoided.
next prev parent reply other threads:[~2024-03-23 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:26 [PATCH] riscv: Improve sbi_ecall() code generation by reordering arguments Alexandre Ghiti
2024-03-22 18:57 ` Atish Patra
2024-03-23 6:26 ` Qingfang Deng [this message]
2024-03-24 18:19 ` Alexandre Ghiti
2024-03-25 3:59 ` [External] " yunhui cui
2024-07-12 10:20 ` patchwork-bot+linux-riscv
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=20240323062625.2488-1-dqfext@gmail.com \
--to=dqfext@gmail.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.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