qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Sergio Lopez" <slp@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	hreitz@redhat.com,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Rust in Qemu BoF followup: Rust vs. qemu platform support
Date: Sat, 18 Sep 2021 15:25:28 +1000	[thread overview]
Message-ID: <YUV4SDIFjpvIfmX1@yekko> (raw)
In-Reply-To: <YUS6kp0l7eiHt/fu@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

On Fri, Sep 17, 2021 at 04:56:02PM +0100, Stefan Hajnoczi wrote:
> On Fri, Sep 17, 2021 at 01:11:56PM +0200, Philippe Mathieu-Daudé wrote:
> > Le ven. 17 sept. 2021 10:58, David Gibson <david@gibson.dropbear.id.au> a
> > écrit :
> > 
> > > Hi all,
> > >
> > > At the qemu-in-rust BoF at KVM Forum, I volunteered to look into
> > > whether Rust supported all the host/build platforms that qemu does,
> > > which is obviously vital if we want to make Rust a non-optional
> > > component of the build
> > >
> > 
> > Could user mode emulation be impacted by this decision? What code used by
> > user emulation could potentially be converted to Rust?
> 
> qemu-user does not have the same security requirements as qemu-system,
> since the application is running under a given uid/gid on the host
> system and can invoke system calls.
> 
> I think the benefits of Rust in qemu-user would be more around
> expressiveness (language constructs like pattern matching, traits, etc)
> and correctness (memory leaks, concurrency, etc). Both benefits might
> motivate someone to write parts of qemu-user in Rust, so I guess the
> answer is "all of it potentially could be converted". It's impossible to
> know until someone contributes patches.

Right.  It certainly could be used there, but I don't know it's the
most promising or interesting area for it.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-09-18  5:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  8:58 Rust in Qemu BoF followup: Rust vs. qemu platform support David Gibson
2021-09-17  9:17 ` Cornelia Huck
2021-09-17  9:54   ` Marc-André Lureau
2021-09-17 11:03     ` David Gibson
2021-09-18 20:01       ` Richard Henderson
2021-09-20  3:41         ` David Gibson
2021-09-20  8:13           ` Peter Maydell
2021-09-21  5:57             ` David Gibson
2021-09-17 10:56   ` David Gibson
2021-09-17 11:11 ` Philippe Mathieu-Daudé
2021-09-17 15:56   ` Stefan Hajnoczi
2021-09-18  5:25     ` David Gibson [this message]
2021-09-17 11:34 ` Daniel P. Berrangé
2021-09-17 15:59   ` Stefan Hajnoczi
2021-09-18  5:28     ` David Gibson
2021-09-17 16:04   ` Warner Losh
2021-09-17 18:39     ` Philippe Mathieu-Daudé
2021-09-17 19:02       ` Warner Losh
2021-09-20  3:53     ` David Gibson
2021-09-20 13:58       ` Ed Maste
2021-09-20  3:43   ` David Gibson
2021-09-20  2:23 ` Brad Smith
2021-09-20  4:07   ` David Gibson

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=YUV4SDIFjpvIfmX1@yekko \
    --to=david@gibson.dropbear.id.au \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=hreitz@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=slp@redhat.com \
    --cc=stefanha@redhat.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).