[ltt-dev] lttng development plan
KOSAKI Motohiro
kosaki.motohiro at jp.fujitsu.com
Thu Jan 22 22:21:43 EST 2009
> Mathieu Desnoyers wrote:
> > * Lai Jiangshan (laijs at cn.fujitsu.com) wrote:
> >> Mathieu Desnoyers wrote:
> >>> Hi Gui,
> >>>
> >>> My short-term roadmap is (those are the show stoppers) :
> >>>
> >>> - Get lttng ascii dump to work.
> >>> - create periodical buffer flush per-cpu timer for data streaming
> >>> - Modify LTTng/lttd/lttv to support variable-sized buffers, so we
> >>> don't have to copy the padding. This implies creating an index in
> >>> lttv when opening the trace to know where the subbuffer start is.
> >>> - Waiting for Lai's channel and event ID management modifications
> >>> following my comments. This is needed so the IDs stays valid for the
> >>> binary->ascii in-kernel converter.
> >>> - Support dynamic frequency scaling on x86.
> >>>
> >>> Other nice-to-have, but not a priority :
> >>>
> >>> - Add support for Performance Monitoring Counters (PMC) so they can be
> >>> dumped in the traces.
> >>> - Put back support for kernel and userspace stack dump so it can be
> >>> connected to any given tracepoint.
> >>> - Linux ABI for fast userspace tracing.
> >>> - Then, add NPTL instrumentation (mutexes, phtreads).
> >>> - 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.
>
> I will use kdump. kdump is in the mainline, I think kdump is better
> than crosscrash & LKCD.
Yup, LKCD was perfectly gone.
please ignore LKCD.
More information about the lttng-dev
mailing list