linux-kernel - Re: [PATCH tip][0/2] ftrace interface for blktrace

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] [day] [month] [year] [list]

Message-ID: <20090126134320.GB18859@elte.hu>
Date:	Mon, 26 Jan 2009 14:43:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, linux-btrace@...r.kernel.org
Subject: Re: [PATCH tip][0/2] ftrace interface for blktrace


* Jens Axboe <jens.axboe@...cle.com> wrote:

> On Fri, Jan 23 2009, Arnaldo Carvalho de Melo wrote:
> > Hi Jens,
> > 
> > 	Here is a third version, that also implements blk_add_trace_msg,
> > using ftrace_vprintk.
> > 
> > 	As soon as the TRACE_ITER_CONTEXT_INFO option is implemented
> > I'll provide the struct trace_event->bin() callback to synthesize the
> > old blktrace record format so that we can test the output of trace_pipe
> > with blkparse -i -.
> > 
> > 	Please let me know if this is acceptable for inclusion on
> > linux-tip.
> 
> Sure, go ahead and add it!

Cool - i've started tracking Arnaldo's patch by picking up the latest 
version into tip/tracing/blktrace and merging it into tip/master.

Arnaldo, could you please check latest tip/master:

   http://people.redhat.com/mingo/tip.git/README

to see whether it's all OK, integrated with the latest tracing bits?

	Ingo
--
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/