On Fri, 8 May 2026 at 15:29, John Levon <[email protected]> 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 <[email protected]> > > M: Jagannathan Raman <[email protected]> > > -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 ? -- PMM
