|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 06/23] xen/riscv: introduce guest riscv,isa string
On 6/22/26 4:09 PM, Jan Beulich wrote: On 17.06.2026 13:17, Oleksii Kurochko wrote:Introduce generation of the riscv,isa string passed to the guest via the Device Tree riscv,isa property. Introduce the per-domain isa string and guest isa bitmap, populated during domain creation by calling init_guest_isa(). Introduce guest_unsupp to filter out ISA extensions that should not be exposed to guests: - f/d/q/v: FPU and vector context save/restore are not yet implemented for guests.I may have asked before - what about Zfinx, Zdinx (and the supposed Zqinx)? They aren't in riscv_isa_ext[], yes, but perhaps wrongly so? And hence they may want at least mentioning? They are not supported by Xen so they aren't in riscv_isa_ext so it looks fine for me. They are not in guest_unsupp as they aren't present in riscv_isa_ext and so it won't be propagated to guest anyway because of: + bitmap_andnot(d->arch.isa, riscv_isa, guest_unsupp, + RISCV_ISA_EXT_MAX);While it isn't in riscv_isa_ext[] I think it is fine not to add them to guest_unsupp, so I will add to the commit message that: ```- Zfinx, Zdinx and Zqinx are not implemented for guests either; as they are not present in the riscv_isa_ext[] array, they can never be set in riscv_isa and thus are never exposed to a guest, so there is no need to list them explicitly in guest_unsupp. ```I think it is fine for now but probably it will need to be reworked in future.
I will add the check before for():
if ( buf && ((size_t)total >= size) )
return -ENOSPC;
Thanks.
~ Oleksii
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |