All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Alessandro Di Federico" <ale@rev.ng>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Anton Johansson" <anjo@rev.ng>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Brian Cain" <bcain@quicinc.com>,
	"Chao Peng" <chao.p.peng@linux.intel.com>,
	cjia@nvidia.com, "Cédric Le Goater" <clg@kaod.org>,
	cw@f00f.org, dhedde@kalrayinc.com,
	"Eric Blake" <eblake@redhat.com>,
	eblot@rivosinc.com,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
	"Auger Eric" <eric.auger@redhat.com>,
	felipe@nutanix.com, iggy@theiggy.com,
	"Warner Losh" <imp@bsdimp.com>, "Jan Kiszka" <jan.kiszka@web.de>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	jidong.xiao@gmail.com, "Jim Shu" <jim.shu@sifive.com>,
	"Joao Martins" <joao.m.martins@oracle.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	"Luc Michel" <luc@lmichel.fr>,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Max Chou" <max.chou@sifive.com>,
	"Mark Burton" <mburton@qti.qualcomm.com>,
	mdean@redhat.com, mimu@linux.vnet.ibm.com,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Phil Mathieu-Daudé" <philmd@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Shameerali Kolothum Thodi"
	<shameerali.kolothum.thodi@huawei.com>,
	"Bernhard Beschow" <shentey@gmail.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Wei Wang" <wei.w.wang@intel.com>,
	z.huo@139.com, "LIU Zhiwei" <zhiwei_liu@linux.alibaba.com>,
	zwu.kernel@gmail.com
Subject: Re: QEMU/KVM Community Call (29/10/24) agenda items?
Date: Tue, 29 Oct 2024 15:52:39 +0000	[thread overview]
Message-ID: <ZyEEx1UWqYin1Spq@redhat.com> (raw)
In-Reply-To: <3a6a8109-196e-49ac-8416-49f69b688e5e@redhat.com>

On Tue, Oct 29, 2024 at 02:05:44PM +0100, Paolo Bonzini wrote:
> I would like to discuss the next steps for Rust bindings, but probably it's
> already too late to have a call today; we can have the discussion on the
> mailing list as well.
> 
> In particular I would like to understand:
> 
> - if it's desirable to have https://lore.kernel.org/qemu-devel/1d6034ef-9e41-4ef4-9a95-d03885b09b2b@redhat.com/
> in QEMU 9.2.
> 
> - if we agree on (the plan of) bringing the Rust PL011 to feature completion
> in 10.0 and at the same time toggling the --enable-rust default from
> "disabled" to "auto"

That sounds like reasonable goal. If PL011 work slips, then we just
punt the enable-rust default change to 10.1.

> I would also like to reach an agreement on how Rust patches enter qemu.git
> (that is, whether via my tree or a new one).

IIUC, we decided we ought to have a rust mailing list for QEMU, such that
Rust patches would be cc'd on qemu-devel & qemu-rust. Along with that it
probably makes sense to have a designated "rust staging" tree that people
can base their work against.

Initially I presume "rust staging" would be for all Rust related work to
flow through. At a later date, then we can devolve maintainership back
to the respective subsystem maintainers, and have "rust staging" solely
be for core rust infrastructure patches.

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



      parent reply	other threads:[~2024-10-29 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  7:24 QEMU/KVM Community Call (29/10/24) agenda items? Alex Bennée
2024-10-29 13:05 ` Paolo Bonzini
2024-10-29 13:44   ` Alex Bennée
2024-10-29 15:09     ` Mark Burton
2024-10-29 15:33     ` Paolo Bonzini
2024-10-29 15:52   ` 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=ZyEEx1UWqYin1Spq@redhat.com \
    --to=berrange@redhat.com \
    --cc=ale@rev.ng \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=anjo@rev.ng \
    --cc=armbru@redhat.com \
    --cc=bcain@quicinc.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cjia@nvidia.com \
    --cc=clg@kaod.org \
    --cc=cw@f00f.org \
    --cc=dhedde@kalrayinc.com \
    --cc=eblake@redhat.com \
    --cc=eblot@rivosinc.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=eduardo@habkost.net \
    --cc=elena.ufimtseva@oracle.com \
    --cc=eric.auger@redhat.com \
    --cc=felipe@nutanix.com \
    --cc=iggy@theiggy.com \
    --cc=imp@bsdimp.com \
    --cc=jan.kiszka@web.de \
    --cc=jgg@nvidia.com \
    --cc=jidong.xiao@gmail.com \
    --cc=jim.shu@sifive.com \
    --cc=joao.m.martins@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=luc@lmichel.fr \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=max.chou@sifive.com \
    --cc=mburton@qti.qualcomm.com \
    --cc=mdean@redhat.com \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shentey@gmail.com \
    --cc=stefanha@gmail.com \
    --cc=thuth@redhat.com \
    --cc=wei.w.wang@intel.com \
    --cc=z.huo@139.com \
    --cc=zhiwei_liu@linux.alibaba.com \
    --cc=zwu.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.