| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20101030141644.GA17206@Krystal> Date: Sat, 30 Oct 2010 10:16:44 -0400 From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> To: loic.minier@...onical.com, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Nicolas Pitre <nico@...xnic.net>, Steve Langasek <steve.langasek@...onical.com> Cc: ltt-dev@...ts.casi.polymtl.ca, linux-kernel@...r.kernel.org Subject: LTTng Mainlining Roadmap Hi everyone, Here is an updated roadmap for the LTTng mainlining. As you will notice, the plan is not exactly to push the LTTng code into the Linux kernel as is, but rather to extract LTTng pieces one by one (it's already modular, so it is quite straightforward) and push them to mainline as individual pieces. This is the approach I have taken for the Tracepoints, which led to very good results. I plan to do the same for the Generic Ring Buffer Library, Trace Clocks, kernel state dump... these can all be splitted into serparate mainlining efforts. The new official URL for the LTTng roadmap is: http://lttng.org/roadmap FYI, I fixed the ARM PMU reservation in LTTng yesterday afternoon and made a new release. So it should now play along nicely with perf counters. Feedback is welcome, Thanks! Mathieu -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists