From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Brian Cain <quic_bcain@quicinc.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Emmanouil Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Zhao Liu" <zhao1.liu@intel.com>,
junjie.mao@intel.com, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PULL 00/12] Rust initial PoC + meson changes for 2024-10-07
Date: Mon, 7 Oct 2024 20:39:25 -0700 [thread overview]
Message-ID: <4f7257d9-662e-43c7-9f02-2434e728f2a3@linaro.org> (raw)
In-Reply-To: <ae024a03-17df-4636-87bb-3d0313f03596@quicinc.com>
Hi Brian,
On 10/7/24 20:27, Brian Cain wrote:>>
>> Aside: Paolo, thanks for your work here!
>>
>>
>> Thanks to Manos, I am just the shepherd. :)
>>
>> So far I think the focus for Rust support has been on device
>> models. But is there any interest in
>> being able to write TCG plugins in Rust
>>
>>
>> Is there a good degree of ABI compatibility across QEMU versions? If
>> so, plugins are external shared libraries and therefore they could be
>> built (with Cargo) independent of any QEMU code.
>>
>> I am not involved in plugins work, so I am not the best person to answer!
>
>
> After watching the recording of Alex's KVM Forum presentation on the
> plugins, he's answered my question -- he described the rust bindings
> specifically as "...might require us to be a little bit more formal
> about specifying a proper API..." -- so maybe not a top priority for now.
>
thanks for your interest around plugins.
As you noticed, we are focused for now on making the API more complete
and useful, before starting to think about extending languages available
to write them.
Rust will be on top of the list for sure!
Regards,
Pierrick
next prev parent reply other threads:[~2024-10-08 3:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 11:03 [PULL 00/12] Rust initial PoC + meson changes for 2024-10-07 Paolo Bonzini
2024-10-07 11:03 ` [PULL 01/12] Require meson version 1.5.0 Paolo Bonzini
2024-10-07 11:03 ` [PULL 02/12] build-sys: Add rust feature option Paolo Bonzini
2024-10-07 11:03 ` [PULL 03/12] configure, meson: detect Rust toolchain Paolo Bonzini
2024-10-07 11:03 ` [PULL 04/12] rust: add bindgen step as a meson dependency Paolo Bonzini
2024-10-07 11:03 ` [PULL 05/12] .gitattributes: add Rust diff and merge attributes Paolo Bonzini
2024-10-07 11:03 ` [PULL 06/12] meson.build: add HAVE_GLIB_WITH_ALIGNED_ALLOC flag Paolo Bonzini
2024-10-07 11:03 ` [PULL 07/12] rust: add crate to expose bindings and interfaces Paolo Bonzini
2024-10-07 11:03 ` [PULL 08/12] rust: add utility procedural macro crate Paolo Bonzini
2024-10-07 11:03 ` [PULL 09/12] rust: add PL011 device model Paolo Bonzini
2024-10-07 11:03 ` [PULL 10/12] meson: fix machine option for x86_version Paolo Bonzini
2024-10-07 11:03 ` [PULL 11/12] meson: define qemu_isa_flags Paolo Bonzini
2024-10-07 11:03 ` [PULL 12/12] meson: ensure -mcx16 is passed when detecting ATOMIC128 Paolo Bonzini
2024-10-07 11:11 ` [PULL 00/12] Rust initial PoC + meson changes for 2024-10-07 Daniel P. Berrangé
2024-10-07 11:26 ` Paolo Bonzini
2024-10-07 11:47 ` Daniel P. Berrangé
2024-10-07 11:52 ` Daniel P. Berrangé
2024-10-07 15:51 ` Paolo Bonzini
2024-10-07 17:56 ` Brian Cain
2024-10-07 19:15 ` Paolo Bonzini
2024-10-08 3:27 ` Brian Cain
2024-10-08 3:39 ` Pierrick Bouvier [this message]
2024-10-08 10:01 ` Alex Bennée
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=4f7257d9-662e-43c7-9f02-2434e728f2a3@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=junjie.mao@intel.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_bcain@quicinc.com \
--cc=zhao1.liu@intel.com \
/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).