From: "Daniel P. Berrangé" <berrange@redhat.com>
To: casantos@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH V4] tracing: install trace events file only if necessary
Date: Tue, 18 Apr 2023 10:00:20 +0100 [thread overview]
Message-ID: <ZD5cJGFrFkpuQHx5@redhat.com> (raw)
In-Reply-To: <20230408010410.281263-1-casantos@redhat.com>
Copying Stefan as the trace subsystem maintainer
On Fri, Apr 07, 2023 at 10:04:10PM -0300, casantos@redhat.com wrote:
> From: Carlos Santos <casantos@redhat.com>
>
> It is not useful when configuring with --enable-trace-backends=nop.
>
> Signed-off-by: Carlos Santos <casantos@redhat.com>
> ---
> Changes v1->v2:
> Install based on chosen trace backend, not on chosen emulators.
> Changes v2->v3:
> Add missing comma
> Changes v3->v4:
> Fix array comparison:
> get_option('trace_backends') != [ 'nop' ]
> not
> get_option('trace_backends') != 'nop'
> ---
> trace/meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/trace/meson.build b/trace/meson.build
> index 8e80be895c..30b1d942eb 100644
> --- a/trace/meson.build
> +++ b/trace/meson.build
> @@ -64,7 +64,7 @@ trace_events_all = custom_target('trace-events-all',
> input: trace_events_files,
> command: [ 'cat', '@INPUT@' ],
> capture: true,
> - install: true,
> + install: get_option('trace_backends') != [ 'nop' ],
> install_dir: qemu_datadir)
>
> if 'ust' in get_option('trace_backends')
> --
> 2.31.1
>
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-04-18 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 1:04 [PATCH V4] tracing: install trace events file only if necessary casantos
2023-04-18 9:00 ` Daniel P. Berrangé [this message]
2023-04-18 19:22 ` Stefan Hajnoczi
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=ZD5cJGFrFkpuQHx5@redhat.com \
--to=berrange@redhat.com \
--cc=casantos@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 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.