From: David Gibson <david@gibson.dropbear.id.au>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, berrange@redhat.com, slp@redhat.com,
cohuck@redhat.com, richard.henderson@linaro.org, f4bug@amsat.org,
emaste@freebsd.org, hreitz@redhat.com, stefanha@redhat.com,
marcandre.lureau@redhat.com, pbonzini@redhat.com,
brad@comstyle.com, alex.bennee@linaro.org, imp@bsdimp.com,
sgarzare@redhat.com
Subject: Rust in Qemu BoF followup 2: Rust toolchain availability
Date: Thu, 30 Sep 2021 11:59:42 +1000 [thread overview]
Message-ID: <YVUaDrf5BXPkZu5r@yekko> (raw)
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
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.
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'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
* I'm not really convinced that the way I've formatted it is
particularly good, but I haven't though of a better alternative.
Contributions to improving this would be most welcomed.
--
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 reply other threads:[~2021-09-30 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 1:59 David Gibson [this message]
2021-09-30 10:30 ` Rust in Qemu BoF followup 2: Rust toolchain availability Peter Maydell
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=YVUaDrf5BXPkZu5r@yekko \
--to=david@gibson.dropbear.id.au \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=cohuck@redhat.com \
--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=peter.maydell@linaro.org \
--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 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).