From: Jeff Law <jeffreyalaw@gmail.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Evan Green <evan@rivosinc.com>,
libc-alpha@sourceware.org
Cc: slewis@rivosinc.com, vineetg@rivosinc.com, palmer@rivosinc.com
Subject: Re: [PATCH 1/2] riscv: Add Linux hwprobe syscall support
Date: Sun, 12 Feb 2023 09:58:53 -0700 [thread overview]
Message-ID: <20ed0257-7fb9-80cf-0dca-114c9bcd15a7@gmail.com> (raw)
In-Reply-To: <c478cce6-1c7b-ae9f-6ee5-8e02113bc76a@linaro.org>
On 2/7/23 06:05, Adhemerval Zanella Netto via Libc-alpha wrote:
>
>
> On 06/02/23 16:48, Evan Green wrote:
>> Add awareness and a thin wrapper function around a new Linux system call
>> that allows callers to get architecture and microarchitecture
>> information about the CPUs from the kernel. This can be used to
>> do things like dynamically choose a memcpy implementation.
>
> Do you want to use this symbol on external projects, for instance to
> implement builtin_cpu_supports (as powerpc does)? If so, it has the
> drawback that such feature will only work on glibc.
What's being built really needs to work outside of glibc as well --
consider GCC's function multi-versioning for example.
Jeff
next prev parent reply other threads:[~2023-02-12 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 19:48 [PATCH 0/2] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2023-02-06 19:48 ` [PATCH 1/2] riscv: Add Linux hwprobe syscall support Evan Green
2023-02-07 13:05 ` Adhemerval Zanella Netto
2023-02-09 20:55 ` Evan Green
2023-02-12 16:58 ` Jeff Law [this message]
2023-02-06 19:48 ` [PATCH 2/2] riscv: Add and use alignment-ignorant memcpy Evan Green
2023-02-06 22:05 ` Richard Henderson
2023-02-09 21:04 ` Evan Green
2023-02-06 21:28 ` [PATCH 0/2] RISC-V: ifunced memcpy using new kernel hwprobe interface Richard Henderson
2023-02-07 12:49 ` Adhemerval Zanella Netto
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=20ed0257-7fb9-80cf-0dca-114c9bcd15a7@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=evan@rivosinc.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=slewis@rivosinc.com \
--cc=vineetg@rivosinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).