From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Konstantin Kostiuk" <kkostiuk@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Eric Blake" <eblake@redhat.com>
Subject: Re: Cleaning up contrib/ and tools/
Date: Wed, 25 Mar 2026 16:54:58 +0000 [thread overview]
Message-ID: <acQTYmtvU92LwKbB@redhat.com> (raw)
In-Reply-To: <CAFEAcA_DEPSoAnEzobryPbqU77QHwqYyxybmdi7KX2wjJqzRhw@mail.gmail.com>
On Wed, Mar 25, 2026 at 04:49:57PM +0000, Peter Maydell wrote:
> On Wed, 25 Mar 2026 at 11:44, Markus Armbruster <armbru@redhat.com> wrote:
> >
> > Peter Maydell <peter.maydell@linaro.org> writes:
> >
> > > We have a couple of directories in our source tree which have
> > > accumulated things in them that don't really belong there; this is a
> > > proposal to clean up by moving things to more appropriate locations
> > > (as 11.1 work, obviously).
> > >
> > > Firstly, contrib/ has a tendency to be a dumping ground for stuff that
> > > we didn't think hard enough about finding a good home for, and for
> > > things in a weird "not really maintained" state. We should either
> > > (a) care enough about something to give it a correct home and to
> > > maintain it, or (b) not care about it, and kick it out of our tree.
> > >
> > > Secondly, tools/ exists but is very under-used. I think it should be
> > > for the set of standalone tools that we build if you configure
> > > --enable-tools and which we document in docs/tools. Currently it
> > > contains two things, one of which doesn't match that idea...
> > >
> > > So, starting with tools/:
> >
> > [...]
> >
> > > And for contrib/, easy ones first:
> > > * contrib/vhost-user-{blk,bridge,gpu,input,scsi} move to tools/
> > > * contrib/elf2dmp moves to tools/
> > > * contrib/ivshmem-client and contrib/ivshmem-server move to tools/
> >
> > Absolutely not. This is example code, provided in the hope of helping
> > people understand the protocol, and experiment with it. It is entirely
> > unfit for more serious use, and that's intentional.
>
> So, example code but we don't think it's a good example ? :-)
>
> Our system documentation seems to assume you're going to run
> ivshmem-server:
>
> https://www.qemu.org/docs/master/system/devices/ivshmem.html
>
> > Perhaps contrib/ is not a good home for example code. It seems to
> > bother people whose judgement I respect. Can we find a better home?
>
> I'm not sure to what extent we should be in the business of
> providing example code. If we are doing that we should label
> it all a bit better...
FWIW, the server does warn the user on startup since Markus commited
a335c6f204eefba8ff935bcee8f31f51d2174119:
+ /*
+ * Do not remove this notice without adding proper error handling!
+ * Start with handling ivshmem_server_send_one_msg() failure.
+ */
+ printf("*** Example code, do not use in production ***\n");
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-03-25 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:09 Cleaning up contrib/ and tools/ Peter Maydell
2026-03-24 17:31 ` Daniel P. Berrangé
2026-03-24 18:28 ` Pierrick Bouvier
2026-03-24 18:33 ` Peter Maydell
2026-03-24 18:44 ` Pierrick Bouvier
2026-03-25 9:21 ` Daniel P. Berrangé
2026-03-25 10:05 ` Marc-André Lureau
2026-03-25 11:11 ` Alex Bennée
2026-03-25 15:17 ` Pierrick Bouvier
2026-03-25 16:43 ` Peter Maydell
2026-03-25 7:42 ` Kostiantyn Kostiuk
2026-03-25 11:43 ` Markus Armbruster
2026-03-25 14:32 ` Alex Bennée
2026-03-25 16:49 ` Peter Maydell
2026-03-25 16:54 ` Daniel P. Berrangé [this message]
2026-03-25 19:41 ` Peter Maydell
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=acQTYmtvU92LwKbB@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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