qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] is anybody experimenting with the idea of rust code in QEMU?
Date: Tue, 21 May 2019 16:48:12 +0200	[thread overview]
Message-ID: <8c07524e-3d2b-da06-2aac-b0eaf3e1c179@redhat.com> (raw)
In-Reply-To: <CAFEAcA-vSebWjhbFTdfOSGHJtr8-a+DKG22JU3tS-1OoGR=VXQ@mail.gmail.com>

On 21/05/19 16:39, Peter Maydell wrote:
> Hi; I have on my todo list the idea of some experimentation/prototyping
> of whether being able to write some components of QEMU in Rust would
> be (a) feasible (b) beneficial (c) fun to play around with even if
> it is likely that it doesn't go anywhere :-)
> 
> I know Paolo has had a look at how you might write some makefiles
> to integrate rust into a C program (https://github.com/bonzini/rust-and-c/).
> Has anybody else been doing anything in this general area ?

I have a version of QEMU's RCU that can be called from Rust code with a
nice API (https://github.com/bonzini/rust-rcu-qemu).  The idea was to
continue with a port of the memory API, and then to use rust-vmm's
virtio code.

Paolo

> (I went to two good talks locally recently about rust-vmm and Amazon's
> 'firecracker' VMM by Andreea Florescu and Diana Popa -- I
> definitely plan to look at rust-vmm as part of this.)
> 
> thanks
> -- PMM
> 



  reply	other threads:[~2019-05-21 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:39 [Qemu-devel] is anybody experimenting with the idea of rust code in QEMU? Peter Maydell
2019-05-21 14:48 ` Paolo Bonzini [this message]
2019-05-21 15:15 ` Marc-André Lureau
2019-05-22 12:53 ` Stefan Hajnoczi
2019-05-22 13:28   ` Paolo Bonzini
2019-05-22 13:52     ` Dr. David Alan Gilbert

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=8c07524e-3d2b-da06-2aac-b0eaf3e1c179@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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).