All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	"Sergio Lopez" <slp@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Ed Maste" <emaste@freebsd.org>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>, Brad <brad@comstyle.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Warner Losh" <imp@bsdimp.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Rust in Qemu BoF followup 2: Rust toolchain availability
Date: Thu, 30 Sep 2021 11:30:20 +0100	[thread overview]
Message-ID: <CAFEAcA_ibRiKmXvo3CDOvLundowVWr3uPKWbkegh95U+d-zfMQ@mail.gmail.com> (raw)
In-Reply-To: <YVUaDrf5BXPkZu5r@yekko>

On Thu, 30 Sept 2021 at 03:21, David Gibson <david@gibson.dropbear.id.au> wrote:
>
> Hi again all,
>
> I've now done.. or at least started... the second part of my followup
> from the KVM Forum BoF on Rust in Qemu.
>
> I've extended the page at https://wiki.qemu.org/RustInQemu with
> information on Rust toolchain availability.  However, I found I had a
> lot more open questions on this one, so there are quite a lot of gaps.

Thanks for doing this work.

I note that we have a new host architecture loongarch64 currently
circling to land. It looks like this is in the "Rust does not have
support for this target" category at the moment.

> In particular:
>  * I haven't so far figured out how to definitively check package
>    information for RHEL & SLES (they're not covered by repology, and
>    RHEL module structure confuses me, even as a RedHatter)
>  * I'm not at all sure what criteria to use to consider something as
>    having "good enough" rustup support, so that information is all
>    blank so far

I guess the answer here is probably "if it has at least the
glibc and kernel minimum versions that are documented as
required for the target-triple in the lists at
https://doc.rust-lang.org/rustc/platform-support.html then
that's 'good enough'".

>  * I've taken a bit of a stab in the dark about what Rust version is
>    recent enough for our purposes (1.31.0).  I strongly suspect we're
>    going to want to move that to something more recent, but I don't
>    know what, which will mean revising a bunch of stuff

Hmm. The more we feel we need features that are from a new
version of Rust the more nervous I get about whether this is
really something we want to jump to just yet. 1.31 is less than
3 years old, which is pretty recent in the context of QEMU's
own distro support policy.

>  * I'm not really convinced that the way I've formatted it is
>     particularly good, but I haven't though of a better alternative.

I guess we might also care about the CPU architecture per distro,
in that even if old version X of the distro supports architecture Y
and rust today supports architecture Y, that doesn't mean that
distro version X's shipped rust supported architecture Y.
But we can probably reasonably say "use rustup" if there are
corner cases like that.

-- PMM


  reply	other threads:[~2021-09-30 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  1:59 Rust in Qemu BoF followup 2: Rust toolchain availability David Gibson
2021-09-30 10:30 ` Peter Maydell [this message]
2021-10-04  6:01   ` David Gibson
2021-09-30 10:45 ` Daniel P. Berrangé
2021-10-07  1:14   ` 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=CAFEAcA_ibRiKmXvo3CDOvLundowVWr3uPKWbkegh95U+d-zfMQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=emaste@freebsd.org \
    --cc=f4bug@amsat.org \
    --cc=hreitz@redhat.com \
    --cc=imp@bsdimp.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.