public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug bpf/29307] New: assembler improvements and tapset porting guide
@ 2022-06-30 16:25 serhei at serhei dot io
  0 siblings, 0 replies; only message in thread
From: serhei at serhei dot io @ 2022-06-30 16:25 UTC (permalink / raw)
  To: systemtap

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-06-30 16:25 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-30 16:25 [Bug bpf/29307] New: assembler improvements and tapset porting guide serhei at serhei dot io

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).