From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] qemu: retain default trace backend if 'ust' is not enabled
Date: Tue, 04 Apr 2023 11:05:05 +0100 [thread overview]
Message-ID: <988002ed9a0e281efeea1d4a4098d486127030e6.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230403143730.26123-1-thomas.de_schampheleire@nokia.com>
On Mon, 2023-04-03 at 16:37 +0200, Thomas De Schampheleire wrote:
> The qemu build system enables the 'log' trace backend by default, if no
> explicit choice was made with '--enable-trace-backend=CHOICE'.
>
> However, the qemu recipe uses the following PACKAGECONFIG line:
> PACKAGECONFIG[ust] = "--enable-trace-backend=ust,--enable-trace-backend=nop,lttng-ust,"
>
> which means that the 'nop' trace backend will be explicitly selected if the
> 'ust' feature is not enabled. The 'nop' backend removes almost all trace
> points at compile time, and thus basically means 'disable tracing'.
>
> To retain the default trace backend if 'ust' is not enabled, the above
> PACKAGECONFIG line should either explicitly fall back to the 'log' backend,
> or not provide any value for the 'disabled' case. This commit chooses the
> latter to not make any assumption about the upstream default.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> meta/recipes-devtools/qemu/qemu.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> index b41055fe5d..ae99a9e87b 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -207,7 +207,7 @@ PACKAGECONFIG[libudev] = "--enable-libudev,--disable-libudev,eudev"
> PACKAGECONFIG[attr] = "--enable-attr,--disable-attr,attr,"
> PACKAGECONFIG[rbd] = "--enable-rbd,--disable-rbd,ceph,ceph"
> PACKAGECONFIG[vhost] = "--enable-vhost-net,--disable-vhost-net,,"
> -PACKAGECONFIG[ust] = "--enable-trace-backend=ust,--enable-trace-backend=nop,lttng-ust,"
> +PACKAGECONFIG[ust] = "--enable-trace-backend=ust,,lttng-ust,"
> PACKAGECONFIG[pie] = "--enable-pie,--disable-pie,,"
> PACKAGECONFIG[seccomp] = "--enable-seccomp,--disable-seccomp,libseccomp"
> # libnfs is currently provided by meta-kodi
This triggered reproducible build test failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2659/steps/12/logs/stdio
which leads to:
http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230403-itxd_s50/packages/diff-html/
i.e. the paths to files is being encoded the target source package
files.
We'll need to resolve that issue before we can turn the default tracing
on.
Cheers,
Richard
next prev parent reply other threads:[~2023-04-04 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:37 [PATCH 1/2] qemu: retain default trace backend if 'ust' is not enabled Thomas De Schampheleire
2023-04-03 14:37 ` [PATCH 2/2] qemu: rename deprecated --enable-trace-backend configure option Thomas De Schampheleire
2023-04-04 10:05 ` Richard Purdie [this message]
2023-04-04 18:32 ` [OE-core] [PATCH 1/2] qemu: retain default trace backend if 'ust' is not enabled Thomas De Schampheleire
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=988002ed9a0e281efeea1d4a4098d486127030e6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.de_schampheleire@nokia.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