Nice, I’m (pleasantly) surprised to learn they’re working on Rust given QEMU’s object-oriented C model. I had assumed it would be too difficult to make ergonomic bindings to, but they seem to have a plan so fingers crossed it goes well.
It’s basically an easier version of glib/gtk bindings. Why easier? Because the public API is not stable so Rust work is not constrained by that (C things can change to favor Rust bindings) and because, and this was just my impression, the surface is smaller in QEMU. glib/gtk Rust bindings are great so I’m optimistic there’s a great approach to be found for QEMU as well.
Source: I introduced Rust support/bindings/device in QEMU.
Thanks for your hard work! We have a crypto accelerator written in Rust (thanks to Rivos) which connects to QEMU via a C file that sets up all the registers, objects, etc. It would be interesting to try the Rust bindings directly at some point.
Nice, I’m (pleasantly) surprised to learn they’re working on Rust given QEMU’s object-oriented C model. I had assumed it would be too difficult to make ergonomic bindings to, but they seem to have a plan so fingers crossed it goes well.
It’s basically an easier version of glib/gtk bindings. Why easier? Because the public API is not stable so Rust work is not constrained by that (C things can change to favor Rust bindings) and because, and this was just my impression, the surface is smaller in QEMU. glib/gtk Rust bindings are great so I’m optimistic there’s a great approach to be found for QEMU as well.
Source: I introduced Rust support/bindings/device in QEMU.
Thanks for your hard work! We have a crypto accelerator written in Rust (thanks to Rivos) which connects to QEMU via a C file that sets up all the registers, objects, etc. It would be interesting to try the Rust bindings directly at some point.