From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/21888] New: bpf variants of log()/etc. functions
Date: Wed, 02 Aug 2017 18:14:00 -0000 [thread overview]
Message-ID: <bug-21888-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=21888
Bug ID: 21888
Summary: bpf variants of log()/etc. functions
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
If runtime=bpf, then log() etc. should relay to { printf(...) } rather than %{
embedded-c %} that won't work under bpf.
Generally review tapset *.stp files to see how many of them can grow a bpf
variant easily. The list of lower level "bpf helper" functions is very small
(kernel tools/include/uapi/linux/bpf.h), so we may need to approximate or stub
out, or let the current error message stay for them.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-08-02 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 18:14 fche at redhat dot com [this message]
2018-07-12 20:03 ` [Bug tapsets/21888] " me at serhei dot io
2018-07-23 16:19 ` me at serhei dot io
2018-08-09 14:33 ` [Bug bpf/21888] " me at serhei dot io
2018-08-17 15:53 ` me at serhei dot io
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-21888-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).