linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Sharon Gabay <Sharon.Gabay@mobileye.com>,
	"linux-trace-users@vger.kernel.org" 
	<linux-trace-users@vger.kernel.org>
Subject: Re: trace-cmd: Using the python wrapping to read trace markers
Date: Mon, 12 Sep 2022 05:58:56 -0400	[thread overview]
Message-ID: <20220912055856.317576fc@rorschach.local.home> (raw)
In-Reply-To: <CAPpZLN4o_O+ePT5YGStZknKCrMvQ17XupP4Y0LfQ=1Y9Cn20PQ@mail.gmail.com>

On Mon, 12 Sep 2022 12:47:09 +0300
Tzvetomir Stoyanov <tz.stoyanov@gmail.com> wrote:

> Hi Sharon,
> 
> >
> > We are using this article to generate trace markers:
> > https://lwn.net/Articles/366796/
> >
> > I am responsible for reading the trace.dat binary into our tools and we are using the trace-cmd python wrapping.  
> 
> The trace-cmd python wrappers are auto generated. The logic for that
> may not be up to date, so I do not know what is the current state of
> those wrappers.

Thanks Tzvetomir for responding, and yes, trace-cruncher is something
to look at in this case.

Sharon,

I and many others that could help out with the wrapper code are
currently attending Linux Plumbers in Dublin (https://lpc.events), and
are not able to look into this at the moment. If we remember ( ;-) )
we'll look at this in a couple of weeks.

-- Steve

      reply	other threads:[~2022-09-12  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 19:55 trace-cmd: Using the python wrapping to read trace markers Sharon Gabay
2022-09-12  9:47 ` Tzvetomir Stoyanov
2022-09-12  9:58   ` Steven Rostedt [this message]

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=20220912055856.317576fc@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=Sharon.Gabay@mobileye.com \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=tz.stoyanov@gmail.com \
    /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 NNTP newsgroup(s).