Hi,
Probably most of you are aware of LTTng since it is already integrated
in Linaro's kernel, in this session I will focus on the new LTTng
patchset which has the following characteristics :
1) The size of the kernel patchset has been shrinked for Linux
distributions by removing all LTTng-specific instrumentation from the tree.
2) The lttng-modules package now implements an ABI based on anonymous
file descriptors (inspired from perf) rather than the full-blown VFS
tree the previous LTTng versions were implementing.
3) lttng-modules now exports trace data and metadata in the CTF (Common
Trace Format).
4) lttng-modules now uses the Generic Ring Buffer Library.
LTTng will probably not enter in the Oneiric Ubuntu kernel, but our
target is to upstream most of our patches before the next LTS.
The purpose of this session is :
- to show the benefit developers and sysadmins have with LTTng
kernel and userspace tracers for debugging and QA;
- to highlight the main differences between the current stable LTTng and
this new patchset and the new tools associated with it;
- to find a way to test LTTng in Oneiric to have something rocking in
the next LTS.
The session will be held in room Jozsef on Wednesday 11th between 12:00
and 13:00, the blueprint associated is here :
https://blueprints.launchpad.net/ubuntu/+spec/other-o-lttng
Thanks,
Julien
Hello all,
I want to introduce myself to the linaro-kernel and linaro-dev lists as I
just started at Linaro today in the role of Kernel Working Group Technical
Lead and will be working closely with all of you on enhancing the ARM Linux
ecosystem. I've been using Linux since 1993 and working with the Linux
kernel for over 10 years for a variety of companies including silicon
vendors, OSVs, and device vendors with a broad variety of experience
including ARM CPU and board bring up, hacking on a variety of device
drivers, maintaining a distro kernel, maintaining a few ARM
sub-architectures, educating HW vendors and new developers about the open
source development model, etc. I've been a bit out of the loop of the open
source community the last 1-2 years and am really excited to be involved
with Linaro working on community-focused technology enablement and
enhancement.
I expect this first week to be mostly focused on reading up on process,
existing deliverables, mailing list archives, etc to wrap my head around
where we are right now and where we're headed with the 11.11 release. I'll
be at LDS and look forward to meeting many of you next week and I want to
encourage anyone who won't be at LDS but has concerns, ideas, questions
related to the kernel WG to drop me an email.
Thanks!
~Deepak
Hello!
A call for hardware needs -- please speak now or hold your peace for
another cycle.
Thanx, Paul
----- Forwarded message from James Westby <james.westby(a)linaro.org> -----
Date: Fri, 29 Apr 2011 18:01:18 -0400
From: James Westby <james.westby(a)linaro.org>
To: techleads(a)linaro.org
Subject: LDS: hardware requirements for next cycle
Hi,
I'm organising a session at LDS to collate and prioritise hardware needs
across Linaro.
https://blueprints.launchpad.net/linaro/+spec/linaro-other-o-hardware-needs
If your team needs some hardware that isn't currently ordered then
either come along to the session, or email me beforehand, and tell me:
* What hardware you need (type, quantity)
* When you need it by
* What you need if for (i.e. what won't be able to happen if you don't
have it)
We'll then be able to use this to come up with a shopping list that we
can request hardware from, and balance priorities if we can't have
everything.
If the request is already on the Hardware wiki page then you don't need
to re-send it.
Also, this isn't to say that if you don't mention it now you can't have
it, but it will be helpful to have a comprehensive snapshot of the
requirements before the session.
Thanks,
James
----- End forwarded message -----
I have created the UDS-session blueprints (blueprints to schedule the UDS
sessions) as
discussed in the meeting this morning. Take a look at the sessions
specially the ownership
and make sure you agree, you will have to run the session at UDS if you are
the assignee (owner).
As it turned out, each major Technical Requirement will have one session,
with the exception of k1
where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most
of the sessions cover
multiple topics, you may need have to co-ordinate with others to run your
session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul,
you need to approve all these blueprints in order to start scheduling them.
Grant,
You have registered sessions for boot architecture and DT, please send me
the blueprints links so I can add them to this table.
Regards,
Mounir
== Device Tree ==
* Sent a couple of u-boot patch to remove useless CONFIG_SYS_BOOTMAPSZ
and redefined CONFIG_OF_LIBFDT for mx51/53
* Tested zImage fix patch set with append-dtb patch
* It seems that RMK opposes to putting dts file in kernel tree
== Non-blocking MMC testing ==
* Some more discussion with Per Porlin on mxs-mmc driver regarding
to non-blocking support. Need to do more testing to understand
if the ~4% performance improvement is expected on mxs-mmc.
== LTP Blueprint ==
* Created the initial blueprint linaro-kernel-o-ras-fix-ltp
* Tried ltp-full-20110228 and ltp-kernel-test package shipped with
Natty (ltp-base-20091231), and saw very different test set and
results.
* Got contacted with Paul Larson who was ever the maintainer of LTP
and now leading the Validation team and using LTP to validating
Linaro images. He may give valuable inputs to the requirements
of this Blueprint.
== Plan ==
* Will work on v2 of sdhci-pltfm&of-consolidation
* Keep drafting blueprint linaro-kernel-o-ras-fix-ltp
--
Regards,
Shawn
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Sent Sedat Dilek yet more sets of diagnostics. This turned out to be a bug in the timers system, which Thomas Gleixner fixed.
* Interviewed another candidate for Kernel WG, also +1.
* Pre-Budapest definition/scheduling work.
* Presented on SMP to the Android System Developers Forum.
* Submitted RCU priority boosting to LKML, got good initial feedback. On track for the 2.6.40 merge window.
== Per Forlin <perfor> ==
=== Highlights ===
* Preparing drafts for 11.11 blueprints
* K7.3 Non-Blocking Request in MMC
* K7.4 eMMC Background Maintenance
* K7.6 SDIO Single Function Support
* K7.10 DMA Engine on ARM
* Started to investigate io-scheduling but ended up studying read
ahead instead. It may turn out that "K7.2 Optimize I/O Scheduling for
Flash" is not the right thing to do for flash performance.
=== Plans ===
* Prepare blueprints for LDS
