From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] trace: Do not try to include QMP commands in user emulation binaries
Date: Tue, 20 Dec 2022 16:06:32 +0100 [thread overview]
Message-ID: <091fed13-063f-b3ad-806d-0822be444d4c@linaro.org> (raw)
In-Reply-To: <20221220150417.26751-1-philmd@linaro.org>
On 20/12/22 16:04, Philippe Mathieu-Daudé wrote:
> QMP is not available on user emulation; there is not monitor.
> Besides, since commit a0e61807a3 ("qapi: Remove QMP events
> and commands from user-mode builds") we don't generate the
> qapi-commands-trace.h header in a user-emulation-only build.
>
> Remove the QMP trace commands from qemu-user binaries.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> trace/meson.build | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/trace/meson.build b/trace/meson.build
> index 26b54714d5..4385afbff0 100644
> --- a/trace/meson.build
> +++ b/trace/meson.build
> @@ -88,4 +88,6 @@ if 'ftrace' in get_option('trace_backends')
> trace_ss.add(files('ftrace.c'))
> endif
> trace_ss.add(files('control.c'))
> -trace_ss.add(files('qmp.c'))
> +if have_system or have_tools or have_ga
Maybe this pattern deserves adding a variable similar to:
have_monitor = have_system or have_tools or have_ga
> + trace_ss.add(files('qmp.c'))
> +endif
next prev parent reply other threads:[~2022-12-20 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 15:04 [PATCH] trace: Do not try to include QMP commands in user emulation binaries Philippe Mathieu-Daudé
2022-12-20 15:06 ` Philippe Mathieu-Daudé [this message]
2022-12-21 1:04 ` 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=091fed13-063f-b3ad-806d-0822be444d4c@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).