From: "Frank Ch. Eigler" <fche@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"William Cohen" <wcohen@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Miroslav Rezanina" <mrezanin@redhat.com>,
ddepaula@redhat.com
Subject: Re: [PATCH-for-5.2 v2] trace: use STAP_SDT_V2 to work around symbol visibility
Date: Thu, 19 Nov 2020 09:38:22 -0500 [thread overview]
Message-ID: <20201119143822.GC23928@redhat.com> (raw)
In-Reply-To: <CAJSP0QUAFLUT22pos0YVagyCyJ=L-bGkGMgBHEVYnSCVX9Mpng@mail.gmail.com>
Hi -
> > Maybe add a comment? (no need to repost if you agree):
> >
> > # Workaround to avoid dtrace(1) produces file with 'hidden'
> > # symbol visibility, define STAP_SDT_V2 to produce 'default'
> > # symbol visibility instead.
> >
> > > + QEMU_CFLAGS="$QEMU_CFLAGS -DSTAP_SDT_V2"
Please note that we don't know how long this behavior will persist.
You are relying on an accident. :-)
Much of the systemtap code doesn't support real STAP_SDT_V2 format,
and /usr/include/sys/sdt.h cannot generate it at all. That macro
tricks only the dtrace-header-generator to suppress the "hidden"
visibility attribute, but doesn't change probe metadata format to the
old V2 (in .probes sections rather than .note.* ELF notes).
We'll try not to break it, but please move toward the more proper
per-solib or per-executable hidden copies of the semaphore objects.
- FChE
next prev parent reply other threads:[~2020-11-19 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 11:27 [PATCH v2] trace: use STAP_SDT_V2 to work around symbol visibility Stefan Hajnoczi
2020-11-19 11:31 ` Daniel P. Berrangé
2020-11-19 11:44 ` [PATCH-for-5.2 " Philippe Mathieu-Daudé
2020-11-19 11:58 ` Stefan Hajnoczi
2020-11-19 14:38 ` Frank Ch. Eigler [this message]
2020-11-19 14:47 ` Stefan Hajnoczi
2020-11-19 12:45 ` [PATCH " Miroslav Rezanina
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=20201119143822.GC23928@redhat.com \
--to=fche@redhat.com \
--cc=berrange@redhat.com \
--cc=ddepaula@redhat.com \
--cc=kraxel@redhat.com \
--cc=mrezanin@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@gmail.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).