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: Wed, 19 Jun 2019 15:02:00 -0000 [thread overview]
Message-ID: <bug-23866-6586-22QpzuJZ4y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23866-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23866
--- Comment #4 from William Cohen <wcohen at redhat dot com> ---
Outline changes to make use of BPF_RAW_TRACEPOINTS
- test and note whether kernel has BPF_PROG_TYPE_RAW_TRACEPOINT available
- reuse the tapsets.cxx for the lkm code to discover the arguments for bpf raw
tracepoints
- modify tapsets.cxx tracepoint_derived_probe::build_args_for_bpf to generate
args for raw_tracepoints
bpf raw tracepoints have a array of elelements pointed to by r1
- modify the generate tracepoint section names to note when using "raw_trace"
- modify stapbpf.cxx to handle "raw_trace" as another section type
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-06-19 15:02 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 [this message]
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
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-22QpzuJZ4y@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).