Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] lttng development plan
Date: Mon, 19 Jan 2009 11:43:09 +0800	[thread overview]
Message-ID: <4973F6CD.5040008@cn.fujitsu.com> (raw)
In-Reply-To: <20090107170544.GA10541@Krystal>

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.

>   - Create an in-kernel event filtering module which connects on
>     LTTng.
>   - Early boot tracing.

What your plan for early boot tracing?

>   - Virtual machine tracing support (time synchronisation).
>   - Cluster and distributed computer tracing support (time
>     synchronisation).
>   - Port kmemtrace, ftrace, blktrace, kvmtrace and others to LTTng.
>     Each could have its own channel.
> 
> Please ask if you need more information on specific items.
> 
> Best regards, and many thanks to Fujitsu for the good work,
> 
> Mathieu
> 
> 
> * Gui Jianfeng (guijianfeng at cn.fujitsu.com) wrote:
>> Hi Mathieu,
>>
>> I'd like to know whether you have a plan or roadmap 
>> for lttng's further developping.
>> If you have one, would you share it?
>>
>> -- 
>> Regards
>> Gui Jianfeng
>>
> 






  reply	other threads:[~2009-01-19  3:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49646F42.5040003@cn.fujitsu.com>
2009-01-07 17:05 ` Mathieu Desnoyers
2009-01-19  3:43   ` Lai Jiangshan [this message]
2009-01-20  1:55     ` Mathieu Desnoyers
2009-01-20  6:58       ` Lai Jiangshan
2009-01-23  3:21         ` KOSAKI Motohiro
2009-01-23  3:21       ` KOSAKI Motohiro
2009-01-23  4:49         ` Mathieu Desnoyers
2009-02-02  4:59   ` Gui Jianfeng
2009-02-03  5:11     ` Mathieu Desnoyers
2009-02-11  6:33       ` Zhaolei
2009-02-11  6:50         ` Mathieu Desnoyers
2009-02-11  7:24           ` Zhaolei
2009-02-11  7:37             ` Mathieu Desnoyers
2009-02-19  8:17               ` Zhaolei
2009-03-02  7:01                 ` Zhaolei
2009-03-03 19:25                   ` Mathieu Desnoyers
2009-03-29  8:41                     ` [ltt-dev] [PATCH 0/3] In-kernel filter module Zhaolei
2009-03-29  8:42                       ` [ltt-dev] [PATCH 1/3] Remove old per-type filter Zhaolei
2009-03-29  8:43                       ` [ltt-dev] [PATCH 2/3] Change ltt_run_filter_functor arguments to support in-kernel filter Zhaolei
2009-03-29  8:44                       ` [ltt-dev] [PATCH 3/3] In-kernel filter module Zhaolei
2009-04-06 17:52                         ` Mathieu Desnoyers
2009-04-07  5:45                           ` Zhaolei
2009-04-07 16:48                             ` Mathieu Desnoyers
2009-04-08  3:19                               ` Zhaolei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4973F6CD.5040008@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox