From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>,
qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: [PATCH-for-9.1 0/7] buildsys: Start shrinking qemu-user build process
Date: Thu, 4 Apr 2024 21:47:50 +0200 [thread overview]
Message-ID: <20240404194757.9343-1-philmd@linaro.org> (raw)
Hi,
While reworking include/exec/ I have to build many configs
to be sure nothing breaks. qemu-user is particularly
sensitive to changes in this directory (mostly because
all user-specific files include "qemu.h", itself including
various exec/ headers). Getting tired of this waste I had
a look at what we pointlessly build. This series is the
beginning of yet another cleanup set.
Regards,
Phil.
Philippe Mathieu-Daudé (7):
ebpf: Restrict to system emulation
yank: Restrict to system emulation
monitor: Rework stubs to simplify user emulation linking
util/qemu-config: Extract QMP commands to qemu-config-qmp.c
hw/core: Restrict reset handlers API to system emulation
hw/core: Move reset.c to hwcore_ss[] source set
hw: Include minimal source set in user emulation build
meson.build | 6 +-
include/qemu/config-file.h | 3 +
hw/core/reset.c | 4 +
stubs/fdset.c | 17 ---
stubs/monitor-core.c | 20 +++-
stubs/monitor.c | 8 +-
util/qemu-config-qmp.c | 206 +++++++++++++++++++++++++++++++++++++
util/qemu-config.c | 204 +-----------------------------------
ebpf/meson.build | 2 +-
hw/core/meson.build | 2 +-
stubs/meson.build | 5 +-
util/meson.build | 3 +-
12 files changed, 248 insertions(+), 232 deletions(-)
delete mode 100644 stubs/fdset.c
create mode 100644 util/qemu-config-qmp.c
--
2.41.0
next reply other threads:[~2024-04-04 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 19:47 Philippe Mathieu-Daudé [this message]
2024-04-04 19:47 ` [PATCH-for-9.1 1/7] ebpf: Restrict to system emulation Philippe Mathieu-Daudé
2024-04-04 22:14 ` Richard Henderson
2024-04-08 6:29 ` Jason Wang
2024-04-04 19:47 ` [PATCH-for-9.1 2/7] yank: " Philippe Mathieu-Daudé
2024-04-04 22:15 ` Richard Henderson
2024-04-08 8:48 ` Paolo Bonzini
2024-04-04 19:47 ` [PATCH-for-9.1 3/7] monitor: Rework stubs to simplify user emulation linking Philippe Mathieu-Daudé
2024-04-08 9:50 ` Paolo Bonzini
2024-04-08 10:59 ` Philippe Mathieu-Daudé
2024-04-04 19:47 ` [PATCH-for-9.1 4/7] util/qemu-config: Extract QMP commands to qemu-config-qmp.c Philippe Mathieu-Daudé
2024-04-08 8:50 ` Paolo Bonzini
2024-04-04 19:47 ` [PATCH-for-9.1 5/7] hw/core: Restrict reset handlers API to system emulation Philippe Mathieu-Daudé
2024-04-08 10:09 ` Paolo Bonzini
2024-04-04 19:47 ` [PATCH-for-9.1 6/7] hw/core: Move reset.c to hwcore_ss[] source set Philippe Mathieu-Daudé
2024-04-05 22:44 ` Richard Henderson
2024-04-08 6:00 ` Philippe Mathieu-Daudé
2024-04-04 19:47 ` [PATCH-for-9.1 7/7] hw: Include minimal source set in user emulation build Philippe Mathieu-Daudé
2024-04-05 22:45 ` Richard Henderson
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=20240404194757.9343-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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;
as well as URLs for NNTP newsgroup(s).