From: "serhei at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/29307] New: assembler improvements and tapset porting guide
Date: Thu, 30 Jun 2022 16:25:44 +0000 [thread overview]
Message-ID: <bug-29307-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29307
Bug ID: 29307
Summary: assembler improvements and tapset porting guide
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: serhei at serhei dot io
Target Milestone: ---
PR created to track improvements to the stapbpf tapsets to make them easier to
contribute to. Relevant products include but not limited to:
(1) 'Porting tapsets to stapbpf' document on the SystemTap Wiki, including an
explanation of what code goes where (there are some conventions with %( %? %)
ifdefs to avoid code duplication)
(2) improvements to the BPF assembler. The current code follows the convention
0xc5, $rc, -, _err, 0; /* jslt $rc, 0, _err */
(comment absolutely necessary to avoid needing to look up opcodes); which was
fine at the beginning but as I contemplate coming back to this and redoing
embedded-C code for several more tapsets, I think it can be vastly improved.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-06-30 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29307-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).