qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	slp@redhat.com, cohuck@redhat.com,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Max Reitz" <hreitz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"David Gibson" <david@gibson.dropbear.id.au>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	sgarzare@redhat.com
Subject: Re: Rust in Qemu BoF followup: Rust vs. qemu platform support
Date: Fri, 17 Sep 2021 13:02:25 -0600	[thread overview]
Message-ID: <CANCZdfpwhvo-efNz3XnPPChaZsyq1v2Q=kO0inguOasm0bVxOQ@mail.gmail.com> (raw)
In-Reply-To: <119693ac-5aed-969a-9d8f-252db75a2d98@amsat.org>

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

On Fri, Sep 17, 2021, 12:39 PM Philippe Mathieu-Daudé <f4bug@amsat.org>
wrote:

> On 9/17/21 6:04 PM, Warner Losh wrote:> wrt FreeBSD:
> >
> > The main focus of the project is on AMD64 (x86_64) and ARM64 (aarc64).
> With
> > ricsv64 being ascendant as well. i386 and armv7 are fading. ppc64 has
> > strong,
> > but episodic, interest as well. The rest are bit players.
> >
> > i386 (i686 really), armv7 and riscv7 are the next tier of interest in
> > FreeBSD
> > land. i386 is confined to 32-bit VMs with only a few legacy hardware
> > deployments
> > still kicking. armv7 is more popular on embedded boards, some of which
> have
> > a need to run qemu.
>
> What part of QEMU is used there, user-emulation (likely IMO) or
> system-emulation (unlikely) or both?
>

System emulation is typical.  User emulation of x86 is the only interesting
thing, but that is less complete than other arch.

> riscv64 has a rust port that's being upstreamed, but not
> > there yet and there's likely interest to run qemu on it for research
> > projects.
> > riscv64 isn't widely deployed but has a lot of developer interest /
> > mindshare.
> > sparc64 was removed from FreeBSD 13 and has been irrelevant for years.
> > ppc 32 bit has some minor interest. mips has been fading fast and stands
> > an excellent chance of being removed before FreeBSD 14 (which is
> currently
> > slated for 2022). PowerPC 64 is hard to talk about... there's interest
> > that comes
> > and goes, but when it's around, it's quite intense. It's quite likely
> > there will
> > be interest to run qemu on ppc64 on FreeBSD, but that's much less
> certain.
> >
> > So it all depends on what having rust means for those platforms that
> > don't have
> > it. Would it be a 'half a loaf' situation where the non-rust bits would
> > be buildable
> > but cool new drivers written in rust won't be? Or will it be so central
> > that rust is
> > table stakes to even start a qemu build? To be honest, I'm not sure this
> > difference
> > would greatly affect the above answer :).
> >
> > Rust works really well on x86_64 and aarch64 (though there's more often
> > a lag
> > on the latter of a few weeks). I know of a rust riscv64 port, but that's
> > just getting
> > ready to upstream. No first-hand or second-hand clue on the rest.
> >
> > FreeBSD tl;dr: x86_64 and aarch64 are must have. i386, armv7 and riscv64
> are
> > really nice to have. ppc64 might also be in that list, but that's less
> > certain. The rest
> > have little to no relevance.
>
> Thanks for gathering this useful info!
>

You are welcome.

Warner

> P.S I've been poking at people to get our QEMU aarch64 CI story in better
> > shape than it is today... I'll have to continue to prompt those
> > interested...
> >
>

[-- Attachment #2: Type: text/html, Size: 3937 bytes --]

  reply	other threads:[~2021-09-17 19:07 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
2021-09-17 16:04   ` Warner Losh
2021-09-17 18:39     ` Philippe Mathieu-Daudé
2021-09-17 19:02       ` Warner Losh [this message]
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='CANCZdfpwhvo-efNz3XnPPChaZsyq1v2Q=kO0inguOasm0bVxOQ@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).