qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Warner Losh <imp@bsdimp.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	pkg-qemu-devel@lists.alioth.debian.org,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	ncopa@alpinelinux.org, bofh@freebsd.org,
	virtualization@gentoo.org, dilfridge@gentoo.org, hi@alyssa.is,
	edolstra+nixpkgs@gmail.com, brad@comstyle.com,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	dvzrv@archlinux.org, anatol.pomozov@gmail.com,
	"Miroslav Rezanina" <mrezanin@redhat.com>
Subject: Re: Rust BoF and maintainer minutes and planning the roadmap to Rust
Date: Tue, 15 Oct 2024 08:23:02 +0100	[thread overview]
Message-ID: <87zfn5akyx.fsf@draig.linaro.org> (raw)
In-Reply-To: <CANCZdfq85yJTkTR3TZQ=XmaeLmfxrQCQj6g-0viFaCidsOKwWQ@mail.gmail.com> (Warner Losh's message of "Mon, 14 Oct 2024 16:45:10 -0600")

Warner Losh <imp@bsdimp.com> writes:

> [[ sorry for the lag $LIFE has been over-full lately ]]

No worries.
>  
>  Obviously you don't have to worry
>  about the Linux kernel but I wonder how much rust userspace you
>  currently have packaged? Do you have the rust-vmm vhost-device binaries
>  for example?
>
> Yes. I believe we build those today.
>
> I expect it to mostly work, most of the time, to be honest on FreeBSD. I also
> expect there to be more breakage than we see with llvm/clang...

I would hope if llvm/clang is working you shouldn't see any additional
breakage due to rust (I don't believe they overly hack llvm for their
use).

> So the bottom line should be that we'll be able to make it work, but there
> is likely going to be more work since rust is less mature than C. However,
> it's not clear if this is an occasional minor thing, or if it becomes major and
> frequent. And the only way to know that is to take the plunge, so don't
> let this stop your plans.

Absolutely. The aim of this exercise was to make sure downstreams are
aware this is coming so it doesn't come as a surprise. I did CC
emulation at freebsd but I got bounced as I was not subscribed. Could
you make the wider FreeBSD community aware of the thread?

>
> Warner

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2024-10-15  7:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 14:23 Rust BoF and maintainer minutes and planning the roadmap to Rust Alex Bennée
2024-09-26 15:03 ` Stefan Hajnoczi
2024-09-30 10:23   ` Alex Bennée
2024-09-30 10:51     ` Stefan Hajnoczi
2024-09-26 16:43 ` Daniel P. Berrangé
2024-09-27  7:28   ` Markus Armbruster
2024-10-22 11:55     ` Paolo Bonzini
2024-09-27  2:06 ` Junjie Mao
2024-10-03  8:53 ` Warner Losh
2024-10-03  8:55   ` Warner Losh
2024-10-03  9:56     ` Alex Bennée
2024-10-03 11:29       ` Michael Tokarev
2024-10-14 22:45       ` Warner Losh
2024-10-15  7:23         ` Alex Bennée [this message]
2024-10-03  9:53   ` Daniel P. Berrangé
2024-10-03 10:04     ` Warner Losh
2024-10-03 10:58   ` Daniel P. Berrangé
2024-10-22 11:10 ` Paolo Bonzini

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=87zfn5akyx.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=anatol.pomozov@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bofh@freebsd.org \
    --cc=brad@comstyle.com \
    --cc=dilfridge@gentoo.org \
    --cc=dvzrv@archlinux.org \
    --cc=edolstra+nixpkgs@gmail.com \
    --cc=hi@alyssa.is \
    --cc=hreitz@redhat.com \
    --cc=imp@bsdimp.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=mjt@tls.msk.ru \
    --cc=mrezanin@redhat.com \
    --cc=ncopa@alpinelinux.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pkg-qemu-devel@lists.alioth.debian.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=virtualization@gentoo.org \
    /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).