From: Richard Henderson <richard.henderson@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
qemu-devel@nongnu.org
Cc: brad@comstyle.com, Alistair.Francis@wdc.com, palmer@dabbelt.com,
qemu-riscv@nongnu.org
Subject: Re: [PATCH 3/3] util/cpuinfo-riscv: Use linux __riscv_hwprobe syscall
Date: Tue, 2 Jul 2024 16:08:21 -0700 [thread overview]
Message-ID: <41d6aa5b-5356-4048-8ef6-291a058f4197@linaro.org> (raw)
In-Reply-To: <793a6bbe-5ac6-400c-b02b-9893a8887ee0@ventanamicro.com>
On 7/2/24 15:15, Daniel Henrique Barboza wrote:
>
>
> On 6/27/24 3:03 PM, Richard Henderson wrote:
>> With recent linux kernels, there is a syscall to probe for various
>> ISA extensions. These bits were phased in over several kernel
>> releases, so we still require checks for symbol availability.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> meson.build | 6 ++++++
>> util/cpuinfo-riscv.c | 26 ++++++++++++++++++++++++++
>> 2 files changed, 32 insertions(+)
>>
>> diff --git a/meson.build b/meson.build
>> index 97e00d6f59..58afd0125d 100644
>> --- a/meson.build
>> +++ b/meson.build
>> @@ -2837,6 +2837,12 @@ have_cpuid_h = cc.links('''
>> }''')
>> config_host_data.set('CONFIG_CPUID_H', have_cpuid_h)
>> +# Don't bother to advertise asm/hwprobe.h for old versions that do
>> +# not contain RISCV_HWPROBE_EXT_ZBA.
>> +config_host_data.set('CONFIG_ASM_HWPROBE_H',
>> + cc.has_header_symbol('asm/hwprobe.h',
>> + 'RISCV_HWPROBE_EXT_ZBA'))
>> +
>
> FWIW I looked around Linux and I think we can snapshot hwprobe support by
> checking for RISCV_HWPROBE_KEY_IMA_EXT_0 (Linux commit 162e4df137c) if we
> ever need hwprobe for exts earlier than ZBA (C and V).
Sure. It'll take some effort to use RVV for TCG vector operations. :-)
>
> Checking for ZBA is fine for this patch though.
>
>
> Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Thanks.
r~
next prev parent reply other threads:[~2024-07-02 23:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 18:03 [PATCH 0/3] util: Add cpuinfo support for riscv Richard Henderson
2024-06-27 18:03 ` [PATCH 1/3] util/cpuinfo-riscv: Support host/cpuinfo.h " Richard Henderson
2024-07-02 19:55 ` Philippe Mathieu-Daudé
2024-07-02 23:04 ` Richard Henderson
2024-07-03 7:32 ` Philippe Mathieu-Daudé
2024-07-02 22:17 ` Daniel Henrique Barboza
2024-07-02 23:56 ` Alistair Francis
2024-07-03 8:46 ` LIU Zhiwei
2024-06-27 18:03 ` [PATCH 2/3] util/cpuinfo-riscv: Support OpenBSD signal frame Richard Henderson
2024-07-02 19:58 ` Philippe Mathieu-Daudé
2024-07-02 22:16 ` Daniel Henrique Barboza
2024-07-02 23:56 ` Alistair Francis
2024-06-27 18:03 ` [PATCH 3/3] util/cpuinfo-riscv: Use linux __riscv_hwprobe syscall Richard Henderson
2024-07-02 22:15 ` Daniel Henrique Barboza
2024-07-02 23:08 ` Richard Henderson [this message]
2024-07-02 23:58 ` Alistair Francis
2024-07-02 16:26 ` [PATCH 0/3] util: Add cpuinfo support for riscv Richard Henderson
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=41d6aa5b-5356-4048-8ef6-291a058f4197@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=brad@comstyle.com \
--cc=dbarboza@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.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;
as well as URLs for NNTP newsgroup(s).