From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: John Levon <john.levon@nutanix.com>,
Jag Raman <jag.raman@oracle.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
"clg@redhat.com" <clg@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] Mark Multi-Process QEMU as Orphaned
Date: Fri, 8 May 2026 16:05:00 +0100 [thread overview]
Message-ID: <af37nA6d8Jdysn2I@redhat.com> (raw)
In-Reply-To: <CAFEAcA_sQahkspZ15NP0Hmw9AedH1pHUv__YL_ww3UtmX=LPDA@mail.gmail.com>
On Fri, May 08, 2026 at 03:39:35PM +0100, Peter Maydell wrote:
> On Fri, 8 May 2026 at 15:29, John Levon <john.levon@nutanix.com> wrote:
> >
> > On Fri, May 08, 2026 at 02:21:37PM +0000, Jag Raman wrote:
> >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 0a90204ae9..ce2b494086 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -4429,7 +4429,7 @@ F: tests/tcg/aarch64/system/semiheap.c
> > > Multi-process QEMU
> > > M: Elena Ufimtseva <elena.ufimtseva@oracle.com>
> > > M: Jagannathan Raman <jag.raman@oracle.com>
> > > -S: Maintained
> > > +S: Orphan
> > > F: docs/devel/multi-process.rst
> > > F: docs/system/multi-process.rst
> > > F: hw/pci-host/remote.c
> > >
> > > Thanks for the reminder, John!
> >
> > (Just for context, Cédric suggested this after my patch to update the
> > libvfio-user submodule for the compilation issues.)
> >
> > > I’ll send a PR shortly removing parts we are not longer using.
> >
> > QEMU maintainers can correct me, but I'd think it has to go through a
> > deprecation cycle first?
>
> That's generally correct. Apart from features which are clearly
> unused because they were actually broken without anybody noticing,
> we have a deprecation cycle where we first list the feature
> in deprecated.rst; then it is in the deprecated state for
> that release and the following one, and can be finally
> removed in the one after that.
>
> However in this case as I understand it the multiprocess
> feature has always been "experimental" (as marked by the
> machine and device names "x-remote", "x-pci-proxy-dev", etc
> having an "x-" prefix). So if we really don't think this is
> likely to be being used by anybody in practice I think the
> experimental state allows us to remove it without waiting.
> Dan, Paolo, what do you think ?
If it was always marked experimental, then we do not need to apply the
deprecation process, though the maintainers can choose to do so at their
discretion.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-05-08 15:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:26 [PATCH] Mark Multi-Process QEMU as Orphaned John Levon
2026-05-08 10:31 ` Peter Maydell
2026-05-08 10:35 ` John Levon
2026-05-08 10:43 ` Peter Maydell
2026-05-08 10:48 ` Philippe Mathieu-Daudé
2026-05-08 14:21 ` Jag Raman
2026-05-08 14:28 ` John Levon
2026-05-08 14:33 ` Jag Raman
2026-05-08 14:37 ` John Levon
2026-05-08 15:07 ` Jagannathan Raman
2026-05-08 15:19 ` John Levon
2026-05-08 15:35 ` Jagannathan Raman
2026-05-08 16:07 ` John Levon
2026-05-21 8:24 ` Cédric Le Goater
2026-05-21 14:41 ` Jag Raman
2026-05-11 16:15 ` Jag Raman
2026-05-11 16:25 ` John Levon
2026-05-11 16:39 ` Jag Raman
2026-05-22 20:48 ` Jag Raman
2026-05-26 9:04 ` John Levon
2026-05-26 15:36 ` Jag Raman
2026-05-08 14:39 ` Peter Maydell
2026-05-08 15:05 ` Daniel P. Berrangé [this message]
2026-05-08 18:28 ` 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=af37nA6d8Jdysn2I@redhat.com \
--to=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.levon@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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.