From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/19396] New: systemtap can't find certain kernel tracepoints
Date: Tue, 22 Dec 2015 21:37:00 -0000 [thread overview]
Message-ID: <bug-19396-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19396
Bug ID: 19396
Summary: systemtap can't find certain kernel tracepoints
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
Commit 7649bb8 updated the support for finding kernel tracepoints. However,
even with this commit, systemtap still can't find certain kernel tracepoints.
There is a script, in src/scripts/tracepoint-diff that points this out.
Here are the missing tracepoints, listed by OS.
RHEL6 (2.6.32-573.3.1.el6.x86_64):
module:module_free
module:module_get
module:module_load
module:module_put
module:module_request
napi:napi_poll
net:net_dev_queue
net:net_dev_xmit
net:netif_receive_skb
net:netif_rx
skb:consume_skb
skb:kfree_skb
skb:skb_copy_datagram_iovec
sock:sock_exceed_buf_limit
sock:sock_rcvqueue_full
udp:udp_fail_queue_rcv_skb
RHEL7 (3.10.0-327.el7.x86_64):
ftrace:function
hda:hda_get_response
hda:hda_send_cmd
hda:hda_unsol_event
module:module_free
module:module_get
module:module_load
module:module_put
module:module_request
xfs:* (353 total xfs tracepoints)
Fedora 23 (4.2.7-300.fc23.x86_64):
ftrace:function
hda:hda_get_response
hda:hda_send_cmd
hda:hda_unsol_event
hda:snd_hdac_stream_start
hda:snd_hdac_stream_stop
module:module_free
module:module_get
module:module_load
module:module_put
module:module_request
regmap:regcache_drop_region
regmap:regcache_sync
regmap:regmap_async_complete_done
regmap:regmap_async_complete_start
regmap:regmap_async_io_complete
regmap:regmap_async_write_start
regmap:regmap_cache_bypass
regmap:regmap_cache_only
regmap:regmap_hw_read_done
regmap:regmap_hw_read_start
regmap:regmap_hw_write_done
regmap:regmap_hw_write_start
regmap:regmap_reg_read
regmap:regmap_reg_read_cache
regmap:regmap_reg_write
snd_pcm:hwptr
snd_pcm:hw_ptr_error
snd_pcm:xrun
vsyscall:emulate_vsyscall
xfs:* (359 total xfs tracepoints)
Fedora Rawhide (4.4.0-0.rc4.git4.1.fc24.x86_64):
ftrace:function
hda:hda_get_response
hda:hda_send_cmd
hda:hda_unsol_event
hda:snd_hdac_stream_start
hda:snd_hdac_stream_stop
module:module_free
module:module_get
module:module_load
module:module_put
module:module_request
regmap:regcache_drop_region
regmap:regcache_sync
regmap:regmap_async_complete_done
regmap:regmap_async_complete_start
regmap:regmap_async_io_complete
regmap:regmap_async_write_start
regmap:regmap_cache_bypass
regmap:regmap_cache_only
regmap:regmap_hw_read_done
regmap:regmap_hw_read_start
regmap:regmap_hw_write_done
regmap:regmap_hw_write_start
regmap:regmap_reg_read
regmap:regmap_reg_read_cache
regmap:regmap_reg_write
snd_pcm:hwptr
snd_pcm:hw_ptr_error
snd_pcm:xrun
vsyscall:emulate_vsyscall
We need to convert the 'tracepoint-diff' script to a test case, so we can know
when systemtap can't find a set of tracepoints.
I've debugged this issue somewhat, and the missing xfs tracepoints are because
we need to add a '-I DIR' gcc option to compiles.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-12-22 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 21:37 dsmith at redhat dot com [this message]
2016-01-06 17:12 ` [Bug translator/19396] " dsmith at redhat dot com
2016-01-06 20:40 ` jistone at redhat dot com
2016-01-06 21:55 ` dsmith at redhat dot com
2016-01-06 21:57 ` dsmith at redhat dot com
2016-01-08 21:46 ` dsmith at redhat dot com
2016-01-08 23:16 ` jistone at redhat dot com
2016-01-11 13:51 ` dsmith 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-19396-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).