Re: [PATCH 11/13] android: persistent_trace: ftrace intopersistent_ram

[Greg KH]

On Wed, Mar 07, 2012 at 01:58:21PM -0800, John Stultz wrote:
> From: Colin Cross <ccross@xxxxxxxxxxx>
> 
> persistent_trace uses the ftrace infrastructure, but traces
> into a persistent_ram buffer instead of the regular ftrace
> ringbuffer.  After a reset or panic, the trace can be
> decoded with cat /sys/kernel/debug/persistent_trace.

Has this patch been run by the tracing kernel developers?

And what's the status on merging the persistent_ram stuff in with the
in-kernel api for this type of thing?  That should then get rid of this
separate tracing module, or at the least, let it be accepted directly by
the tracing developers and not need to go through staging, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/