From: Conor Dooley <conor@kernel.org>
To: Juhan Jin <juhan.jin@foxmail.com>
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
jpoimboe@kernel.org, juhanj2@illinois.edu,
alexghiti@rivosinc.com, samuel.holland@sifive.com,
palmer@dabbelt.com, ajones@ventanamicro.com
Subject: Re: Is RISC-V Static Call worth implementing ?
Date: Fri, 13 Sep 2024 21:55:14 +0100 [thread overview]
Message-ID: <20240913-spearfish-feeble-4c0032f37484@spud> (raw)
In-Reply-To: <tencent_24E1437DFC1D2BB7528A2A28D503C8033107@qq.com>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
On Fri, Sep 13, 2024 at 03:05:33AM -0500, Juhan Jin wrote:
> Hi folks,
>
> I’m interested in implementing Static Call for RISC-V, and I want to
> know whether it is worth the efforts to implement Static Call for
> RISC-V.
>
> Does the aforementioned benefits merit a RISC-V static call implementation
> (especially inline)? Or are the benefits so negligible that it’s simply not
> worth the effort to do a RISC-V implementation?
Pretty sure we've talked about wanting it before - Samuel, Alex, Drew
Jones or Palmer might remember best what exactly we wanted it for
however, as I do not.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-09-13 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 8:05 Is RISC-V Static Call worth implementing ? Juhan Jin
2024-09-13 20:55 ` Conor Dooley [this message]
2024-09-13 23:50 ` Samuel Holland
2024-09-14 13:34 ` Andrew Jones
2024-09-13 22:42 ` Charlie Jenkins
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=20240913-spearfish-feeble-4c0032f37484@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=jpoimboe@kernel.org \
--cc=juhan.jin@foxmail.com \
--cc=juhanj2@illinois.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--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