qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QEMU PPC VLE support


From: Daniel P . Berrangé
Subject: Re: QEMU PPC VLE support
Date: Thu, 15 Dec 2022 14:06:15 +0000
User-agent: Mutt/2.2.7 (2022-08-07)

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 :|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]