From: Jan Beulich <jbeulich@suse.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: xen-devel@lists.xenproject.org,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bob Eshleman" <bobbyeshleman@gmail.com>,
"Connor Davis" <connojdavis@gmail.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Conor Dooley" <conor@kernel.org>
Subject: Re: [PATCH v3] xen/riscv: identify specific ISA supported by cpu
Date: Thu, 6 Feb 2025 17:39:06 +0100 [thread overview]
Message-ID: <db3edc3d-5d91-4c6a-8b97-52048df9e800@suse.com> (raw)
In-Reply-To: <585eff97-af33-4bfd-be10-fdacbb9b9069@gmail.com>
On 06.02.2025 14:05, Oleksii Kurochko wrote:
> On 2/5/25 8:07 PM, Conor Dooley wrote:
>> Yo,
>>
>> On Thu, Jan 23, 2025 at 03:46:36PM +0100, Oleksii Kurochko wrote:
>>> Supported ISA extensions are specified in the device tree within the CPU
>>> node, using two properties: `riscv,isa-extensions` and `riscv,isa`.
>>>
>>> Currently, Xen does not support the `riscv,isa-extensions` property, as
>>> all available device tree source (DTS) files in the Linux kernel (v6.12-rc3)
>>> and DTBs generated by QEMU use only the `riscv,isa` property.
>> That's not true? The riscv,isa-extensions property went into linux in
>> late 2023 (6.7 or so) and QEMU in v9.0.0 about a year ago, so all source
>> files in linux and blobs generated by QEMU should have both. OpenSBI &
>> U-Boot support both also. Might not affect your decision about what to
>> support here - but the rationale provided for implementing the deprecated
>> (per the binding at least) property isn't accurate.
>
> I confused something with Linux kernel sources. Double-check and riscv,isa-extensions
> is really supported.
>
> Regarding QEMU, at the momemnt, Xen uses Debian bookworm and the following version
> is used:
> QEMU emulator version 7.2.11 (Debian 1:7.2+dfsg-7+deb12u6)
>
> I will update the commit message.
>
> Do you ( Conor and Jan ) think that it makes sense to support deprecated property?
> Or it would be better start to use QEMU v9.0.0 and just drop support for deprecated property?
Unless there's a guarantee that all actual hardware we'd ever run on would
offer the new property, we might be better off supporting both. In no case
should we take only qemu into account, imo.
Jan
next prev parent reply other threads:[~2025-02-06 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 14:46 [PATCH v3] xen/riscv: identify specific ISA supported by cpu Oleksii Kurochko
2025-01-27 14:47 ` Jan Beulich
2025-02-03 15:05 ` Oleksii Kurochko
2025-02-03 16:03 ` Jan Beulich
2025-02-03 16:24 ` Oleksii Kurochko
2025-02-03 16:31 ` Jan Beulich
2025-02-05 19:07 ` Conor Dooley
2025-02-06 13:05 ` Oleksii Kurochko
2025-02-06 16:39 ` Jan Beulich [this message]
2025-02-06 17:46 ` Conor Dooley
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=db3edc3d-5d91-4c6a-8b97-52048df9e800@suse.com \
--to=jbeulich@suse.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bobbyeshleman@gmail.com \
--cc=connojdavis@gmail.com \
--cc=conor@kernel.org \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.