From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf
Date: Tue, 16 Jul 2019 18:20:00 -0000 [thread overview]
Message-ID: <bug-23866-6586-yE0iR3CdK0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23866-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23866
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #11907|0 |1
is obsolete| |
--- Comment #8 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11909
--> https://sourceware.org/bugzilla/attachment.cgi?id=11909&action=edit
Revised version of the WIP bpf raw tracepoint support
This patch includes configurations machinery to eliminate the stapbfp bpf raw
tracepoints stuff that requires some additional data structure fields and enum
types that are not available on RHEL7.
The access the various fields look reasonable in the following example:
$ uname -a
Linux localhost.localdomain 5.3.0-0.rc0.git4.1.fc31.x86_64 #1 SMP Fri Jul 12
13:34:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ ../install/bin/stap -k -e 'probe kernel.trace("sched_switch"){printf("%d
%s(%d) %s(%d)\n", $preempt, kernel_string($prev->comm), $prev->pid,
kernel_string($next->comm), $next->pid)}' -T 0.01
1 stapio(1505) systemd-journal(576)
0 systemd-journal(576) rcu_sched(11)
0 rcu_sched(11) ksoftirqd/0(10)
0 ksoftirqd/0(10) rcu_sched(11)
0 rcu_sched(11) stapio(1505)
0 stapio(1505) stapio(1508)
0 stapio(1508) swapper/0(0)
0 swapper/0(0) rcu_sched(11)
0 rcu_sched(11) swapper/0(0)
Keeping temporary directory "/tmp/stapto4iHA"
$ more /proc/576/comm
systemd-journal
$ more /proc/11/comm
rcu_sched
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-07-16 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:31 [Bug translator/23866] New: " fche at redhat dot com
2019-06-10 14:53 ` [Bug translator/23866] " fche at redhat dot com
2019-06-10 15:58 ` wcohen at redhat dot com
2019-06-12 14:22 ` wcohen at redhat dot com
2019-06-19 15:02 ` wcohen at redhat dot com
2019-06-25 13:40 ` wcohen at redhat dot com
2019-07-10 15:02 ` wcohen at redhat dot com
2019-07-15 20:00 ` wcohen at redhat dot com
2019-07-16 18:20 ` wcohen at redhat dot com [this message]
2019-07-18 14:43 ` wcohen at redhat dot com
2019-07-18 16:02 ` 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-23866-6586-yE0iR3CdK0@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).