From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, "David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
qemu-arm@nongnu.org, "Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Song Gao" <gaosong@loongson.cn>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v3 0/4] target: Restrict 'qapi-commands-machine.h' to system emulation
Date: Thu, 23 Feb 2023 13:43:36 +0100 [thread overview]
Message-ID: <20230223124340.95367-1-philmd@linaro.org> (raw)
All series reviewed, can patches be picked by corresponding
maintainers, or should I include them in on of my PRs?
The "qapi-commands-machine.h" header is not generated in user-only
emulation. This series removes its use in user-emu code by moving
the QMP code depending on this header into a separate sysemu unit.
Since v2:
- Rebased
- Renamed target/$foo/monitor.c -> target/$foo/$foo-qmp-cmds.c (Markus)
Since v1:
- renamed cpu-monitor.c -> monitor.c on loongarch
Philippe Mathieu-Daudé (4):
target/arm: Restrict 'qapi-commands-machine.h' to system emulation
target/i386: Restrict 'qapi-commands-machine.h' to system emulation
target/loongarch: Restrict 'qapi-commands-machine.h' to system
emulation
target/ppc: Restrict 'qapi-commands-machine.h' to system emulation
target/arm/{monitor.c => arm-qmp-cmds.c} | 28 +++++++++
target/arm/helper.c | 29 ----------
target/arm/meson.build | 2 +-
target/i386/cpu.c | 74 +++++++++++++-----------
target/loongarch/cpu.c | 27 ---------
target/loongarch/loongarch-qmp-cmds.c | 37 ++++++++++++
target/loongarch/meson.build | 1 +
target/ppc/cpu-qom.h | 2 +
target/ppc/cpu_init.c | 48 +--------------
target/ppc/meson.build | 2 +-
target/ppc/{monitor.c => ppc-qmp-cmds.c} | 50 +++++++++++++++-
11 files changed, 159 insertions(+), 141 deletions(-)
rename target/arm/{monitor.c => arm-qmp-cmds.c} (90%)
create mode 100644 target/loongarch/loongarch-qmp-cmds.c
rename target/ppc/{monitor.c => ppc-qmp-cmds.c} (78%)
--
2.38.1
next reply other threads:[~2023-02-23 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:43 Philippe Mathieu-Daudé [this message]
2023-02-23 12:43 ` [PATCH v3 1/4] target/arm: Restrict 'qapi-commands-machine.h' to system emulation Philippe Mathieu-Daudé
2023-02-23 13:40 ` Markus Armbruster
2023-02-23 12:43 ` [PATCH v3 2/4] target/i386: " Philippe Mathieu-Daudé
2023-02-23 12:43 ` [PATCH v3 3/4] target/loongarch: " Philippe Mathieu-Daudé
2023-02-23 13:41 ` Markus Armbruster
2023-02-23 12:43 ` [PATCH v3 4/4] target/ppc: " Philippe Mathieu-Daudé
2023-02-23 13:42 ` Markus Armbruster
2023-02-23 13:49 ` [PATCH v3 0/4] target: " Markus Armbruster
2023-02-23 15:56 ` Philippe Mathieu-Daudé
2023-02-23 15:58 ` Philippe Mathieu-Daudé
2023-02-23 16:25 ` Markus Armbruster
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=20230223124340.95367-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=gaosong@loongson.cn \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=yangxiaojuan@loongson.cn \
/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).