From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Viktor Prutyanov" <viktor.prutyanov@phystech.edu>,
"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH 0/9] tools: Move more tools sources into tools/
Date: Mon, 11 May 2026 11:05:26 +0200 [thread overview]
Message-ID: <agGb1m4paju1pIN9@redhat.com> (raw)
In-Reply-To: <20260508152428.2648560-1-peter.maydell@linaro.org>
Am 08.05.2026 um 17:24 hat Peter Maydell geschrieben:
> We have a set of binaries that we call "tools": they're built based on
> the --enable-tools/--disable-tools configure setting, they're
> documented in docs/tools, and they're standalone executables of one
> form or another.
>
> Currently the sources for these are a bit scattered: many still in the
> top level source directory, some in contrib, one or two actually in
> the tools directory.
>
> As an initial attempt at cleanup, this patchset moves the sources for
> qemu-bridge-helper, qemu-edid, qemu-img, qemu-io, qemu-nbd,
> qemu-keymap, qemu-vmsr-helper and elf2dmp into the tools/ directory.
>
> The patchseries also moves the ebfp skeleton sources from tools/ebpf/
> to ebpf/bpf-src/, because this isn't a tool by the above definition.
>
> As per my thread from a while back, I would ultimately like us to
> clean up contrib/:
> https://lore.kernel.org/qemu-devel/CAFEAcA_5HvGriDsWnb1ALuA_dgG320eKv7yuM2kThv=rfOSZQA@mail.gmail.com/
> But parts of that clearly need more discussion. So this is just doing
> some parts that I hope are not controversial.
>
> Annoyingly, meson doesn't seem to provide any way for a subdirectory
> meson.build to say "the foo.c in this subdir builds into a foo
> executable that lives at the top level of the builddir". And we have a
> lot of test harness stuff plus user muscle memory that assumes that
> qemu-img and qemu-io live there. So the build runes for these tools
> have to stay in the top level meson.build (and tools/meson.build
> remains an empty file). The exception is that contrib/elf2dmp/elf2dmp
> is now tools/elf2dmp/elf2dmp, but I think the set of people who were
> running that from the build directory will be small.
Should qemu-storage-daemon be moved as well? I never particularly liked
the storage-daemon/ directory that Paolo created in 7c58bb76 and that
singled qemu-storage-daemon out among the tools. If the binary could
move whereever all the other tools live, too, that would be even better.
Kevin
next prev parent reply other threads:[~2026-05-11 9:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:24 [PATCH 0/9] tools: Move more tools sources into tools/ Peter Maydell
2026-05-08 15:24 ` [PATCH 1/9] ebpf: move ebpf skeleton source to ebpf/ directory Peter Maydell
2026-05-08 16:07 ` Daniel P. Berrangé
2026-05-27 6:35 ` Philippe Mathieu-Daudé
2026-05-08 15:24 ` [PATCH 2/9] tools: Move qemu-bridge-helper sources to tools/ directory Peter Maydell
2026-05-08 15:24 ` [PATCH 3/9] tools: Move qemu-edid " Peter Maydell
2026-05-08 15:24 ` [PATCH 4/9] tools: Move qemu-img " Peter Maydell
2026-05-08 15:24 ` [PATCH 5/9] tools: Move qemu-io " Peter Maydell
2026-05-08 15:24 ` [PATCH 6/9] tools: Move qemu-nbd " Peter Maydell
2026-05-08 15:24 ` [PATCH 7/9] tools: Move qemu-keymap " Peter Maydell
2026-05-08 15:24 ` [PATCH 8/9] tools: Move qemu-vmsr-helper up a directory level Peter Maydell
2026-05-12 6:53 ` Akihiko Odaki
2026-05-12 8:45 ` Peter Maydell
2026-05-08 15:24 ` [PATCH 9/9] tools: Move elf2dmp from contrib/ to tools/ Peter Maydell
2026-05-08 16:00 ` [PATCH 0/9] tools: Move more tools sources into tools/ Pierrick Bouvier
2026-05-08 16:22 ` Peter Maydell
2026-05-10 20:23 ` Marc-André Lureau
2026-05-11 8:37 ` Daniel P. Berrangé
2026-05-11 9:27 ` Peter Maydell
2026-05-11 16:56 ` Pierrick Bouvier
2026-05-08 16:02 ` Pierrick Bouvier
2026-05-11 9:05 ` Kevin Wolf [this message]
2026-05-11 9:21 ` 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=agGb1m4paju1pIN9@redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=viktor.prutyanov@phystech.edu \
--cc=vsementsov@yandex-team.ru \
/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.