From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] Updated LTTng project roadmap
Date: Wed, 24 Feb 2010 12:19:17 -0500 [thread overview]
Message-ID: <20100224171917.GA8798@Krystal> (raw)
Hi everyone,
I just updated the LTTng project roadmap, available here:
lttng.org > Project Status > ROADMAP
http://lttng.org/cgi-bin/gitweb.cgi?p=lttv.git;a=blob_plain;f=doc/developer/lttng-lttv-roadmap.html
The most important part is the "LTT Next Generation Roadmap TODO (high
priority)" section. Here are the highlights:
(1) LTTng event description: move from tracepoint/markers to Ftrace TRACE_EVENT
declarations. Extend TRACE_EVENT as needed. (Douglas Santos)
(1) LTTng ring buffer adaptation for FTrace.
(1) FTrace/LTTng trace format standardization.
(1) Extend NO_HZ support vs trace streaming support to other architectures (need
to add cpu idle notifiers and test).
(1) Make sure ltt-ascii kernel text dump fits well with streaming hooked into
cpu idle.
[Depends on cpu idle notifier port to other architectures]
(1) Support CPUs with scalable frequency with a time-consistent increment and
with an approach scalable to SMP. (done for ARM OMAP3 UP only, but the OMAP3
approach should be tested and probably derived into an SMP implementation)
(3) LTTng trace session (support multiple active traces at once) integration
into Ftrace.
(3) LTTng and Ftrace DebugFS interface merge.
(3) LTTng trace clock time-stamping merge into mainline.
(3) NMI-safe tracing merge.
So if these items are important to you, contributions in developer-hours or
funding are welcome.
I'll do my best to keep this page more up-to-date in the future.
Thanks !
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency Consultant
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2010-02-24 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100224171917.GA8798@Krystal \
--to=mathieu.desnoyers@efficios.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