qemu-rust.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Chao Liu(openatom.club)" <chao.liu@openatom.club>
To: "Paolo Bonzini" <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: Re: From HUST OpenAtom Club: Inquiry & Contribution Plan for Rust In QEMU
Date: Wed, 22 Oct 2025 23:51:06 +0800	[thread overview]
Message-ID: <e0f03fac-2a16-439f-9a22-2015c18ba739@openatom.club> (raw)
In-Reply-To: <cc709134-2d28-4ac5-b7fe-c61bd1c5ccbf@redhat.com>

On 10/20/2025 11:22 PM, Paolo Bonzini wrote:
> On 10/20/25 12:56, Chao Liu(openatom.club) wrote:
>> Our initial plan is to add Rust versions of peripheral models for some
>> simple peripherals, such as block devices or I2C devices.
> 
> Yes, this is a good idea.  I2C would add a second bus in addition to sysbus and could show the limitation of the existing bindings.
> 
> Several simple devices in such hw/misc/i2c-echo.c, hw/gpio/pcf8574.c or hw/rtc/ds1338.c could be converted to Rust in the same way as pl011 or hpet.
> 
> For now, avoid devices that have properties (e.g. hw/sensor/tmp105.c).
> 
> Block devices are substantially more complex, so I'd stay with something simple for now.
> 
> Paolo
> 

Hi Paolo,

Thank you for your suggestions, which have been very helpful to us!

Currently, we are referring to the Rust implementation of sysbus to develop
the Rust version of I2CBus, and we have already made some phased progress.

Going forward, we will submit some RFC patches to the upstream for
everyone to discuss.

Thanks,
Chao

>> 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
>>
>>
>


      reply	other threads:[~2025-10-22 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 10:56 From HUST OpenAtom Club: Inquiry & Contribution Plan for Rust In QEMU Chao Liu(openatom.club)
2025-10-20 15:22 ` Paolo Bonzini
2025-10-22 15:51   ` Chao Liu(openatom.club) [this message]

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=e0f03fac-2a16-439f-9a22-2015c18ba739@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).