From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/27152] New: Missing tracepoints for for stap --bpf -L 'kernel.trace("*")'
Date: Tue, 05 Jan 2021 19:46:09 +0000 [thread overview]
Message-ID: <bug-27152-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27152
Bug ID: 27152
Summary: Missing tracepoints for for stap --bpf -L
'kernel.trace("*")'
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
The expectation is that both the traditional kernel module backend and bpf back
would report the same set of trace points however the following returns no
tracepoints:
$ ../install/bin/stap --bpf -l 'kernel.trace("*")' |wc
0 0 0
Include the --compatible=4.1 option and there are many tracepoints reported
$ ../install/bin/stap --compatible=4.1 --bpf -l 'kernel.trace("*")' |wc
2235 16451 260254
The number of tracepoints reported is not quite as many as the traditional stap
kernel module backend:
$ ../install/bin/stap -l 'kernel.trace("*")' |wc
2365 14367 232387
This was observed with locally built systemtap commit
6cb54128e005d1220a7b064ee42b9f72561c28e7 using a Fedora 32
5.9.16-100.fc32.x86_64 kernel.
Looks like the search in collect_raw_tracepoint() from commit
fcdd71babea2435601e5e7f8b6b5faae4a663443 is not finding the various raw
tracepoints.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-01-05 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 19:46 wcohen at redhat dot com [this message]
2021-01-06 19:23 ` [Bug bpf/27152] " wcohen at redhat dot com
2021-01-11 3:45 ` wcohen at redhat dot com
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=bug-27152-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).