Re: [RFC PATCH 00/25] Introduce xenbindgen to autogen hypercall structs

["Teddy Astie" <teddy.astie@xxxxxxxxxx>]

Le 21/11/2024 à 18:46, Anthony PERARD a écrit :
> Instead of creating your own IDL specification, did you look for
> existing project that would do just that? That is been able to describe
> the existing ABI in IDL and use an existing project to generate C and
> Rust headers.
>
> I kind of look into this, but there's quite a few project to explore and
> I didn't really spend enough time. Also, there's probably quite a lot
> that are for client-server interfaces rather than syscall/hypercalls, or
> they impose a data format.
>

I think a such IDL would be C headers, but it's easy to make C headers
that are hard to deal with in other languages. I checked briefly, and
there is Fuchsia IDL that could be interesting in that matter but is
much more complex than what we may be looking for.

>
> Next, on the file format choice, is TOML the best for describing an ABI,
> or would other existing file format make it a bit easier to read, like
> JSON or YAML? (I quite like using YAML so I have a bias toward it 🙂,
> and that's the format used for the CI). I don't think it mater much for
> Serde which file format is used.

It can be decided by making examples of IDL files in various formats and
deciding on which one would be the most readable/easy to deal with.

Teddy


Teddy Astie | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech