From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, rjones@redhat.com, fche@redhat.com,
kraxel@redhat.com, wcohen@redhat.com, mrezanin@redhat.com,
ddepaula@redhat.com
Subject: Re: [PATCH] trace: use STAP_SDT_V2 to work around symbol visibility
Date: Wed, 18 Nov 2020 17:51:28 +0000 [thread overview]
Message-ID: <20201118175128.GH229461@redhat.com> (raw)
In-Reply-To: <20201118174809.686094-1-stefanha@redhat.com>
On Wed, Nov 18, 2020 at 05:48:09PM +0000, Stefan Hajnoczi wrote:
> QEMU binaries no longer launch successfully with recent SystemTap
> releases. This is because modular QEMU builds link the sdt semaphores
> into the main binary instead of into the shared objects where they are
> used. The symbol visibility of semaphores is 'hidden' and the dynamic
> linker prints an error during module loading:
>
> $ ./configure --enable-trace-backends=dtrace --enable-modules ...
> ...
> Failed to open module: /builddir/build/BUILD/qemu-4.2.0/s390x-softmmu/../block-curl.so: undefined symbol: qemu_curl_close_semaphore
>
> The long-term solution is to generate per-module dtrace .o files and
> link them into the module instead of the main binary.
>
> In the short term we can define STAP_SDT_V2 so /usr/bin/dtrace produces
> an .o file with 'default' symbol visibility instead of 'hidden'. This
> workaround is small and easier to merge for QEMU 5.2.
>
> Cc: Daniel P. Berrangé <berrange@redhat.com>
> Cc: wcohen@redhat.com
> Cc: fche@redhat.com
> Cc: kraxel@redhat.com
> Cc: rjones@redhat.com
> Cc: mrezanin@redhat.com
> Cc: ddepaula@redhat.com
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> trace/meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/trace/meson.build b/trace/meson.build
> index d5fc45c628..52be7c5b2c 100644
> --- a/trace/meson.build
> +++ b/trace/meson.build
> @@ -44,7 +44,7 @@ foreach dir : [ '.' ] + trace_events_subdirs
> trace_dtrace_o = custom_target(fmt.format('trace-dtrace', 'o'),
> output: fmt.format('trace-dtrace', 'o'),
> input: trace_dtrace,
> - command: [ 'dtrace', '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ])
> + command: [ 'dtrace', '-DSTAP_SDT_V2', '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ])
I'm a little concerned that we're not also setting this macro before
including the generated trace.h headers, because those headers do
check this STAP_SDT_V1 symbol.
Currently the generated headers have same code for V2 and V3 (the default),
so we won't break, but I'm concerned we could break if they introduce a
future V4 and that impacts the generated headers.
So I think the safe thing todo is set -DSTAP_SDT_V2 as a global compile
arg for QEMU too, so all trace.h files see the symbol that matches the
trace.o files
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:[~2020-11-18 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 17:48 [PATCH] trace: use STAP_SDT_V2 to work around symbol visibility Stefan Hajnoczi
2020-11-18 17:51 ` Daniel P. Berrangé [this message]
2020-11-19 9:44 ` 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=20201118175128.GH229461@redhat.com \
--to=berrange@redhat.com \
--cc=ddepaula@redhat.com \
--cc=fche@redhat.com \
--cc=kraxel@redhat.com \
--cc=mrezanin@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@redhat.com \
--cc=wcohen@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).