All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: peter.maydell@linaro.org,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	slp@redhat.com, cohuck@redhat.com, qemu-devel@nongnu.org,
	f4bug@amsat.org, hreitz@redhat.com, marcandre.lureau@redhat.com,
	pbonzini@redhat.com, alex.bennee@linaro.org, sgarzare@redhat.com
Subject: Re: Rust in Qemu BoF followup: Rust vs. qemu platform support
Date: Sat, 18 Sep 2021 15:28:41 +1000	[thread overview]
Message-ID: <YUV5CWwomyckJVIN@yekko> (raw)
In-Reply-To: <YUS7TUQ11WtyqCMf@stefanha-x1.localdomain>

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

On Fri, Sep 17, 2021 at 04:59:09PM +0100, Stefan Hajnoczi wrote:
65;6402;1c> On Fri, Sep 17, 2021 at 12:34:29PM +0100, Daniel P. Berrangé wrote:
> > On Fri, Sep 17, 2021 at 06:58:37PM +1000, David Gibson wrote:
> > > 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.
> > > 
> > > I've added the information to our wiki at:
> > > 	https://wiki.qemu.org/RustInQemu
> > > 
> > > TBH, the coverage is not as good as I expected.  Linux, macOS and
> > > Windows are pretty much ok, with the exception of Linux on Sparc.
> > > There are a lot of gaps in *BSD support, however.
> > 
> > To me the coverage looks pretty much what I'd expect to need
> > for QEMU - almost all boxes that I'd want to see green are
> > green, except OpenBSD, possibly x86 32-bit for *BSD and
> > sparc(64) on Linux.
> > 
> > Mostly it highlights that we've never explicitly declared what
> > our architecture coverage is intended to be. We do check host
> > arches in configure, but we didn't distinguish this by OS and
> > I think that's a mistake.
> > 
> > In terms of our CI coverage, the only non-x86 testing we do
> > is for Linux based systems.
> > 
> > Although its possible people use non-x86 on non-Linux, I don't
> > recall any discussions/bugs/patches targetting this situation,
> > so if we do have users I doubt there's many.
> 
> macOS on Apple silicon is a non-x86 non-Linux host platform that is
> currently receiving some developer attention. Luckily
> aarch64-apple-darwin is in Tier 2 with host tools.

Yeah, I was figuring macOS on aarch64 would be important with macOS
moving to ARM.  But as you say, that is ok in rust.  Not so much
"luckily" as that being a consequence of it being a fairly active
platform in general.

-- 
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:39 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
2021-09-17 11:34 ` Daniel P. Berrangé
2021-09-17 15:59   ` Stefan Hajnoczi
2021-09-18  5:28     ` David Gibson [this message]
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=YUV5CWwomyckJVIN@yekko \
    --to=david@gibson.dropbear.id.au \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --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 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.