From: "Chao Liu(openatom.club)" <chao.liu@openatom.club>
To: <pbonzini@redhat.com>, <zhao1.liu@intel.com>,
<manos.pitsidianakis@linaro.org>, <marcandre.lureau@redhat.com>,
<philmd@linaro.org>
Cc: <qemu-rust@nongnu.org>, <qemu-devel@nongnu.org>,
<dzm91@openatom.club>, <luojia@openatom.club>
Subject: From HUST OpenAtom Club: Inquiry & Contribution Plan for Rust In QEMU
Date: Mon, 20 Oct 2025 18:56:28 +0800 [thread overview]
Message-ID: <822f8543-10d0-4669-b484-cbd9837e324c@openatom.club> (raw)
Hi,
We are the OpenAtom Open Source Club[1] of Huazhong University of Science
and Technology(HUST). Recently, we have established a new group focusing
on the Rust In QEMU, aiming to make some contributions to the upstream.
Prior to this, we have already achieved some results in the field of
open-source basic software and education using Rust. For example, we
lead the development of RustSBI[2], an open-source firmware written in
Rust, that has been adopted as a reference implementation by the
RISC-V SBI Specification.
We also hosted a QEMU open-source learning training camp[3] in China,
with the number of registrants currently approaching 1,000. In the
training camp's curriculum system, we included contents related to
Rust for QEMU and continuously shared the latest progress of the
QEMU upstream.
We have reviewed the progress of Rust in the recent QEMU versions,
and the results are very encouraging. Rust is basically in a usable
state for QEMU peripheral modeling.
Our initial plan is to add Rust versions of peripheral models for some
simple peripherals, such as block devices or I2C devices.
In addition, we hope to get some other suggestions on what other suitable
work we can do regarding Rust In QEMU.
We look forward to your reply and hope to contribute to the Rust In QEMU~
Link:
[1] HUST OpenAtom Open Source Club:
https://hust.openatom.club/news/20250812_intro_to_club/
[2] RustSBI Github Repo:
https://github.com/rustsbi/rustsbi
[3] Learning QEMU Camp:
https://opencamp.cn/qemu/camp/2025
Thanks,
Chao
next reply other threads:[~2025-10-20 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 10:56 Chao Liu(openatom.club) [this message]
2025-10-20 15:22 ` From HUST OpenAtom Club: Inquiry & Contribution Plan for Rust In QEMU Paolo Bonzini
2025-10-22 15:51 ` Chao Liu(openatom.club)
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=822f8543-10d0-4669-b484-cbd9837e324c@openatom.club \
--to=chao.liu@openatom.club \
--cc=dzm91@openatom.club \
--cc=luojia@openatom.club \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--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).