From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B2BA93858D28; Mon, 11 Oct 2021 15:53:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B2BA93858D28 From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug tapsets/28443] New: Provide syscall_any tapset for bpf Date: Mon, 11 Oct 2021 15:53:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wcohen at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: systemtap@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Systemtap mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2021 15:53:47 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28443 Bug ID: 28443 Summary: Provide syscall_any tapset for bpf Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: tapsets Assignee: systemtap at sourceware dot org Reporter: wcohen at redhat dot com Target Milestone: --- A number of systemtap examples use the syscall_any tapset. Providing a BPF version of the syscall_any tapset would allow additional examples to run wi= th as BPF. Looked into how to implement this. The raw tracepoints sys_enter and sys_e= xit make the pt_regs available. The sys_enter also has $id (don't know why they didn't decide to include $id in the sys_exit). A helper function can pick o= ut the appropriate register from the pt_regs to get the syscall number. The bpf backend also provides information about which target architecture the machi= ne is. As experiment I was ableo to put guards around the initiatization code= in each of the tapset/linux/*/syscall_num.stp files to made the initializer on= ly run on the specific architecture and then have symbolic links from tapset/b= pf to the arch-specific syscall_num.stp files. Will need to add the generatio= n of these guards to scripts/dump-syscalls.sh. Haven't seen a way to get information whether this is 32-bit user-space code running on 64-bit platform. The existing tapset code to do that is using C include files to get bit mask to determine whether things are running in co= mpat mode. There doesn't seem to be a BPF function to extract that information. --=20 You are receiving this mail because: You are the assignee for the bug.=