lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0907202148140.11494@gandalf.stny.rr.com>
Date:	Mon, 20 Jul 2009 21:51:46 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Johannes Berg <johannes@...solutions.net>
cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: binary ftrace buffer format


On Mon, 13 Jul 2009, Johannes Berg wrote:

> Hi!
> 
> For the past hour or so I've been trying to make Steven's rb-read.pl
> script [1] work, but not only is it endian-challenged, working only on
> LE, but also does it seems to have a different idea of the ring buffer
> format, so even with fixes I can't get it to print proper data.
> 
> I'm convinced that it would be trivial to write a program to parse the
> binary trace buffer, but I can't find a format description. Can somebody
> point me to one please?

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

> 
> Oh and a tangential question -- that thing seems to work on pages, does
> that mean I can't trace something larger than a page?

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.

-- Steve


> 
> johannes
> 
> [1] http://lwn.net/Articles/321777/
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ