From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: Rust in QEMU roadmap
Date: Wed, 27 Nov 2024 14:46:21 +0800 [thread overview]
Message-ID: <Z0bAPQxjwyc15Hyv@intel.com> (raw)
In-Reply-To: <cc40943e-dec1-4890-a1d9-579350ce296f@pbonzini.local>
On Tue, Nov 26, 2024 at 06:46:45PM +0100, Paolo Bonzini wrote:
> Date: Tue, 26 Nov 2024 18:46:45 +0100
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: Rust in QEMU roadmap
> X-Mailer: git-send-email 2.47.0
>
> [several people are in bcc. You can follow the thread at
> https://lore.kernel.org/r/cc40943e-dec1-4890-a1d9-579350ce296f@pbonzini.local]
>
> Based on the content presented in the community calls, here are some
> ideas for future Rust in QEMU subprojects.
>
> This is by no means exhaustive, for example QAPI and async (block devices)
> are missing because I have not looked at them.
>
> Table of contents
> '''''''''''''''''
>
> * Status in QEMU 9.2
> * Build system
> * Feature parity for pl011 device
> * Avoiding undefined behavior
> * Safe QOM class definitions
> * QOM method calls
> * Callbacks
> * Tracing/logging
> * Data structure interoperability
> * Features expected from recent rust
Hi Paolo, thanks for your sharing and summary, do you have the plan
about custom allocator (QemuAllocator in rust/qemu-api/src/lib.rs)?
Regards,
Zhao
next prev parent reply other threads:[~2024-11-27 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 17:46 Rust in QEMU roadmap Paolo Bonzini
2024-11-27 6:46 ` Zhao Liu [this message]
2024-11-27 8:21 ` Paolo Bonzini
2024-11-27 10:47 ` Stefan Hajnoczi
2024-11-27 12:18 ` Daniel P. Berrangé
2024-11-27 12:22 ` Paolo Bonzini
2024-12-05 12:00 ` Daniel P. Berrangé
2024-12-05 12:10 ` Paul Durrant
2024-11-27 12:38 ` Daniel P. Berrangé
[not found] <ab7626bb-7c77-49c9-8dc8-86d79b095e3a@pbonzini.local>
2024-12-01 12:16 ` Paolo Bonzini
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=Z0bAPQxjwyc15Hyv@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.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.