From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/23160] 4.17 breaks syscalls tapset
Date: Fri, 15 Jun 2018 21:23:00 -0000 [thread overview]
Message-ID: <bug-23160-6586-XtPWDsOs1C@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23160-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23160
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
Created attachment 11073
--> https://sourceware.org/bugzilla/attachment.cgi?id=11073&action=edit
adaptation example for syscall.read
This patch is an example of the adaptation of syscall.read to both 4.17 and the
tracepoint (bug #14690) as fallbacks. The gist is to factor out the
registers.stp-based argument fetching code into a separate macro, and to
introduce a new embedded-c function to set the context uregs to the pt_regs*
struct we get with either the 4.17 style syscall wrapper or the tracepoints.
... now to repeat some 330 times ... eww
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-06-15 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 18:01 [Bug tapsets/23160] New: " fche at redhat dot com
2018-05-11 21:27 ` [Bug tapsets/23160] " fche at redhat dot com
2018-06-15 21:23 ` fche at redhat dot com [this message]
2018-07-03 13:33 ` mcermak at redhat dot com
2018-07-09 18:16 ` fche at redhat dot com
2018-10-11 13:27 ` juddin 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-23160-6586-XtPWDsOs1C@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).