mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: binary ftrace buffer format
Date: Tue, 21 Jul 2009 12:46:39 +0200	[thread overview]
Message-ID: <1248173199.11045.0.camel@johannes.local> (raw)
In-Reply-To: <alpine.DEB.2.00.0907202148140.11494@gandalf.stny.rr.com>

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On Mon, 2009-07-20 at 21:51 -0400, Steven Rostedt wrote:

> I have a tool called trace-cmd (I'm looking into porting it to the perf 
> tool) but it currently does what you want. I've tested it on both 32 bit 
> and 64 bit systems as well as big and little endians. The files can be 
> created on one system and read on another. It contains data in the files 
> to let other systems know how to read it.
> 
> You can get the tool here:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

Nice! I'll give it a whirl, in the meantime I've already found the
problem I was looking for though.

> Currently, we have not the need to trace more than a page. But this is 
> something that can be changed in the future, but currently we have not had 
> the need, and when it was developed, Linus suggested pages would be fine.

Fair enough.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-07-21 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 21:23 Johannes Berg
2009-07-14 17:22 ` Johannes Berg
2009-07-21  1:51 ` Steven Rostedt
2009-07-21 10:46   ` Johannes Berg [this message]
2009-07-22 11:36   ` Johannes Berg
2009-07-22 15:17     ` Steven Rostedt

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=1248173199.11045.0.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®