* [PATCH v2] qemu-trace-stap: changing SYSTEMTAP_TAPSET considered harmful.
@ 2021-04-09 10:58 Gerd Hoffmann
2021-04-09 11:17 ` Daniel P. Berrangé
0 siblings, 1 reply; 3+ messages in thread
From: Gerd Hoffmann @ 2021-04-09 10:58 UTC (permalink / raw)
To: qemu-devel; +Cc: Gerd Hoffmann, Stefan Hajnoczi
Setting SYSTEMTAP_TAPSET to some value other than
/usr/share/systemtap/tapsets results in systemtap not finding the
standard tapset library any more, which in turn breaks tracing because
pid() and other standard systemtap functions are not available any more.
So using SYSTEMTAP_TAPSET to point systemtap to the qemu probes will
only work for the prefix=/usr installs because both qemu and system
tapsets in the same directory then. All other prefixes are broken.
Fix that by using the "-I $tapsetdir" command line switch instead.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
scripts/qemu-trace-stap | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/scripts/qemu-trace-stap b/scripts/qemu-trace-stap
index 90527eb974f4..eb6e951ff235 100755
--- a/scripts/qemu-trace-stap
+++ b/scripts/qemu-trace-stap
@@ -55,11 +55,6 @@ def tapset_dir(binary):
return os.path.realpath(tapset)
-def tapset_env(tapset_dir):
- tenv = copy.copy(os.environ)
- tenv["SYSTEMTAP_TAPSET"] = tapset_dir
- return tenv
-
def cmd_run(args):
prefix = probe_prefix(args.binary)
tapsets = tapset_dir(args.binary)
@@ -81,11 +76,11 @@ def cmd_run(args):
# We request an 8MB buffer, since the stap default 1MB buffer
# can be easily overflowed by frequently firing QEMU traces
- stapargs = ["stap", "-s", "8"]
+ stapargs = ["stap", "-s", "8", "-I", tapsets ]
if args.pid is not None:
stapargs.extend(["-x", args.pid])
stapargs.extend(["-e", script])
- subprocess.call(stapargs, env=tapset_env(tapsets))
+ subprocess.call(stapargs)
def cmd_list(args):
@@ -101,10 +96,9 @@ def cmd_list(args):
if verbose:
print("Listing probes with name '%s'" % script)
- proc = subprocess.Popen(["stap", "-l", script],
+ proc = subprocess.Popen(["stap", "-I", tapsets, "-l", script],
stdout=subprocess.PIPE,
- universal_newlines=True,
- env=tapset_env(tapsets))
+ universal_newlines=True)
out, err = proc.communicate()
if proc.returncode != 0:
print("No probes found, are the tapsets installed in %s" % tapset_dir(args.binary))
--
2.30.2
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] qemu-trace-stap: changing SYSTEMTAP_TAPSET considered harmful.
2021-04-09 10:58 [PATCH v2] qemu-trace-stap: changing SYSTEMTAP_TAPSET considered harmful Gerd Hoffmann
@ 2021-04-09 11:17 ` Daniel P. Berrangé
2021-04-09 11:43 ` Gerd Hoffmann
0 siblings, 1 reply; 3+ messages in thread
From: Daniel P. Berrangé @ 2021-04-09 11:17 UTC (permalink / raw)
To: Gerd Hoffmann; +Cc: qemu-devel, Stefan Hajnoczi
On Fri, Apr 09, 2021 at 12:58:10PM +0200, Gerd Hoffmann wrote:
> Setting SYSTEMTAP_TAPSET to some value other than
> /usr/share/systemtap/tapsets results in systemtap not finding the
> standard tapset library any more, which in turn breaks tracing because
> pid() and other standard systemtap functions are not available any more.
>
> So using SYSTEMTAP_TAPSET to point systemtap to the qemu probes will
> only work for the prefix=/usr installs because both qemu and system
> tapsets in the same directory then. All other prefixes are broken.
>
> Fix that by using the "-I $tapsetdir" command line switch instead.
Do you know if "-I tapsetdir" appends or prepends to the search path ?
We need it to prepend to ensure that we override any QEMU stp files
that might be already present in /usr/share from an RPM provided
QEMU binary.
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 :|
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] qemu-trace-stap: changing SYSTEMTAP_TAPSET considered harmful.
2021-04-09 11:17 ` Daniel P. Berrangé
@ 2021-04-09 11:43 ` Gerd Hoffmann
0 siblings, 0 replies; 3+ messages in thread
From: Gerd Hoffmann @ 2021-04-09 11:43 UTC (permalink / raw)
To: Daniel P. Berrangé; +Cc: qemu-devel, Stefan Hajnoczi
On Fri, Apr 09, 2021 at 12:17:28PM +0100, Daniel P. Berrangé wrote:
> On Fri, Apr 09, 2021 at 12:58:10PM +0200, Gerd Hoffmann wrote:
> > Setting SYSTEMTAP_TAPSET to some value other than
> > /usr/share/systemtap/tapsets results in systemtap not finding the
> > standard tapset library any more, which in turn breaks tracing because
> > pid() and other standard systemtap functions are not available any more.
> >
> > So using SYSTEMTAP_TAPSET to point systemtap to the qemu probes will
> > only work for the prefix=/usr installs because both qemu and system
> > tapsets in the same directory then. All other prefixes are broken.
> >
> > Fix that by using the "-I $tapsetdir" command line switch instead.
>
> Do you know if "-I tapsetdir" appends or prepends to the search path ?
>
> We need it to prepend to ensure that we override any QEMU stp files
> that might be already present in /usr/share from an RPM provided
> QEMU binary.
Dunno, "man stap" isn't clear on that one. strace shows the files in
the SYSTEMTAP_TAPSET directory are read first. That doesn't imply those
probes have a higher priority though.
take care,
Gerd
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-04-09 11:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-04-09 10:58 [PATCH v2] qemu-trace-stap: changing SYSTEMTAP_TAPSET considered harmful Gerd Hoffmann
2021-04-09 11:17 ` Daniel P. Berrangé
2021-04-09 11:43 ` Gerd Hoffmann
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).