From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Ralf-Philipp Weinmann" <ralf@comsecuris.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: QEMU PPC VLE support
Date: Thu, 15 Dec 2022 14:06:15 +0000 [thread overview]
Message-ID: <Y5sp11VXr/nY84ib@redhat.com> (raw)
In-Reply-To: <CAJSP0QVVQLueQDzOb-GAhORetK38EzgBhem=UjChJ3oaxRaFmg@mail.gmail.com>
On Thu, Dec 15, 2022 at 08:37:54AM -0500, Stefan Hajnoczi wrote:
> Hi,
> I came across this post where Ralf-Philipp is looking for a freelancer
> to implement PPC VLE support in QEMU:
> https://chaos.social/@rpw/109516326028642262
>
> It mentions upstreaming the code and I've included QEMU PPC
> maintainers in this email so they can discuss the project with
> Ralf-Philipp. That way the chances of a mergable result will be
> maximized.
>
> The Rust aspect is interesting, but QEMU does not have any existing
> targets implemented in Rust. It might be a major effort to create the
> necessary C<->Rust interfacing, so I'm not sure whether that's
> realistic given the timeframe for the project.
I'd very much like to see QEMU open up to use of Rust, but I don't
think we should be doing it in a piecemeal way where we special case
just one part.
If we're going to accept use of Rust, then its important that we
(the QEMU community) come to some general agreement for what our
intention is for the use fo Rust in QEMU
Running a paid-for development effort that intends to upstream
to QEMU feels like a pretty risky venture if it intends to use
Rust, prior to the QEMU community making a clear plan about our
wishes for use of Rust.
On the other hand, perhaps such an effort could force us to
actually make a decision. We've talked about Rust quite a few
times, but until someone has a concrete proposal for use of
Rust in QEMU context, we're likely to keep punting the decision
to a later date.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2022-12-15 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 13:37 QEMU PPC VLE support Stefan Hajnoczi
2022-12-15 13:50 ` Philippe Mathieu-Daudé
2022-12-15 13:51 ` Ralf-Philipp Weinmann
2022-12-15 14:06 ` Stefan Hajnoczi
2022-12-15 14:15 ` Ralf-Philipp Weinmann
2022-12-15 13:57 ` Peter Maydell
2022-12-15 14:06 ` Daniel P. Berrangé [this message]
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=Y5sp11VXr/nY84ib@redhat.com \
--to=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=ralf@comsecuris.com \
--cc=richard.henderson@linaro.org \
--cc=stefanha@gmail.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).