From mboxrd@z Thu Jan  1 00:00:00 1970
From: kosaki.motohiro@jp.fujitsu.com (KOSAKI Motohiro)
Date: Fri, 23 Jan 2009 12:21:48 +0900 (JST)
Subject: [ltt-dev] lttng development plan
In-Reply-To: <20090120015553.GD9224@Krystal>
References: <4973F6CD.5040008@cn.fujitsu.com> <20090120015553.GD9224@Krystal>
Message-ID: <20090123213907.34DC.KOSAKI.MOTOHIRO@jp.fujitsu.com>

> > >   - Integrate LTTng with LKCD, test with kernel crash extraction,
> > >     create tools to simplify extraction of traces from crashed kernel,
> > >     integrate those tools to ltt-control.
> > 
> > We will implement it.
> > 
> 
> Great :) Note that there has already been some work done on this. This
> in available as an addition to the crosscrash tool :
> 
> http://sourceforge.net/projects/crosscrash/
> 
> There is a cross-crash-ltt.patch file available on the project website,
> but I think it has not been updated since 2007. Some integration work
> will have to be done.
> 
> Also outputting the traces in the video card's memory would be a
> nice-to-have, because this memory often survives hot reboots.

Just dumb question.

Do you receive this feature requesting from anybody?

Currently, expected flight-recored mode user is enterprise guys.
They usually use crash dumps. then, kernel panic cause tons i/o anyway 
although tracing infomation don't.

Then, this feature doesn't reduce rebooting times, I think.