public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf
Date: Wed, 10 Jul 2019 15:02:00 -0000	[thread overview]
Message-ID: <bug-23866-6586-wZYVqTi23O@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23866-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23866

--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11901
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11901&action=edit
Revised version of the patch that gets

This patch makes some changes in the data structure to make it so the same
argument discovery code can be used for both regular and raw tracepoints.
This current version attempt to get the arguments for the various bpf raw
tracepoints.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2019-07-10 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 21:31 [Bug translator/23866] New: " fche at redhat dot com
2019-06-10 14:53 ` [Bug translator/23866] " fche at redhat dot com
2019-06-10 15:58 ` wcohen at redhat dot com
2019-06-12 14:22 ` wcohen at redhat dot com
2019-06-19 15:02 ` wcohen at redhat dot com
2019-06-25 13:40 ` wcohen at redhat dot com
2019-07-10 15:02 ` wcohen at redhat dot com [this message]
2019-07-15 20:00 ` wcohen at redhat dot com
2019-07-16 18:20 ` wcohen at redhat dot com
2019-07-18 14:43 ` wcohen at redhat dot com
2019-07-18 16:02 ` wcohen 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-23866-6586-wZYVqTi23O@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).