From: David Gibson <david@gibson.dropbear.id.au>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Sergio Lopez" <slp@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>, QEMU <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
hreitz@redhat.com, "Stefan Hajnoczi" <stefanha@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: Fri, 17 Sep 2021 21:03:34 +1000 [thread overview]
Message-ID: <YUR2BjppxkBo8mD0@yekko> (raw)
In-Reply-To: <CAJ+F1CJJvqVQrG5iPXV2s7oLbduHfAhHs0pHdZ8XbxLkNi42VQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3596 bytes --]
On Fri, Sep 17, 2021 at 01:54:22PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Sep 17, 2021 at 1:19 PM Cornelia Huck <cohuck@redhat.com> wrote:
>
> > On Fri, Sep 17 2021, David Gibson <david@gibson.dropbear.id.au> 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
> >
> > Thank you for doing that!
> >
> >
> Yes, the condensed coloured matrix is much more readable than the Rust long
> list. I wonder if they would also adopt it :)
So, in this case we have the relatively small matrix of qemu supported
build OSes by qemu supported build ISAs. For the Rust page there's a
much larger list of OSes, and a somewhat larger list of ISAs. Or
larger still since it's really ABIs they're listing there rather than
just ISAs. And lots of that matrix would be missing for all the OSes
that only support a handful of ISAs. So I think trying to do it as a
matrix there would get pretty unwieldy.
> > > 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.
> >
> > Yes :(
>
> Can we say reasonably that QEMU is supported on *BSD other than x86 (and
> aarch64?), I wonder. Maybe we should consider moving those under the
> unsupported rank.
Yeah, that was my first question as well. I included it all since the
qemu page doesn't qualify the list of OSes/archs, but I did wonder if
anyone is really using obscure archs with a BSD.
> > Do we actually have an idea what we would require? I'm surprised that
> > there are so many targets without host tools or without std support (but
> > maybe they are only missing small things.)
>
> For sparc 32, it was added to support Gentoo at that time which didn't
> switch to 64-bit yet (https://github.com/rust-lang/rust/pull/48297)
>
> For the past 2-3y, Gentoo sparc is now 64 bit. (like Debian apparently for
> a while)
>
> But apparently, by lack of CI it was downgraded to Tier-3.
>
> Is it reasonable to officially drop support for sparc 32 in QEMU
> too?
As a qemu build arch I would say probably yes. As a qemu *target*
arch, probably not. Qemu targets aren't really relevant to this
discussion, but I'm clarifying since if someone sees "XXX arch support
in qemu" without context they'll probably think of target arch before
host arch.
> > > I've included some notes on where the information comes from, and some
> > > uncertainties in there.
> > >
> > > I've made an effort to get the information correct, but double
> > > checking would be appreciated.
> >
> > I did not spot any errors on a quick cross check, but I'm not really
> > sure about what the BSDs support.
> >
> > >
> > > I haven't yet looked into the packaging situation for the Rust
> > > toolchain on various platforms and distros, but I still intend to do
> > > so.
> >
> >
> >
> I would share our wiki page on r/rust if you don't mind, as there are
> various people that can help us fill the gaps I think.
Fine by me.
--
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 --]
next prev parent reply other threads:[~2021-09-17 11:08 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 [this message]
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
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=YUR2BjppxkBo8mD0@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@gmail.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).