|
From: | Philippe Mathieu-Daudé |
Subject: | Re: [PATCH RESEND v2 0/5] target: Restrict 'qapi-commands-machine.h' to system emulation |
Date: | Fri, 13 Jan 2023 15:42:52 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 |
On 13/1/23 14:57, Markus Armbruster wrote:
Philippe Mathieu-Daudé <philmd@linaro.org> writes:[resend fixing my last name typography...] All series reviewed, can patches be picked by corresponding maintainers? 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 v1: - renamed cpu-monitor.c -> monitor.c on loongarchQuick drive-by remark: we usually name C files containing just QMP commands SUBSYSTEM-qmp-cmds.c, and files containing just HMP commands SUBSYSTEM-hmp-cmds.c. On the other hand, the existing monitor-related files seem to be named target/TARGET/monitor.c. Keeping QMP and HMP two separate is desirable, but not required. monitor.c is a fine name for a file containing both.
$ git ls-files | fgrep qmp-cmds.c block/monitor/bitmap-qmp-cmds.c hw/core/machine-qmp-cmds.c hw/pci/pci-qmp-cmds.c monitor/qmp-cmds.c qom/qom-qmp-cmds.c tests/unit/test-qmp-cmds.c $ git ls-files | fgrep monitor.c monitor/monitor.c softmmu/qdev-monitor.c stubs/monitor.c target/arm/monitor.c target/i386/monitor.c target/m68k/monitor.c target/mips/sysemu/monitor.c target/nios2/monitor.c target/ppc/monitor.c target/riscv/monitor.c target/sh4/monitor.c target/sparc/monitor.c target/xtensa/monitor.c tests/unit/test-util-filemonitor.c Do you rather 'cpu-qmp-cmds.c'? Or is your SUBSYSTEM the $target here? Because , target/arm/arm-qmp-cmds.c sounds redundant.
[Prev in Thread] | Current Thread | [Next in Thread] |