2.6.33 patches

To apply, extract the patches and the series file. If you have 'quilt', extract
the file directly into the top level of the kernel source tree (the top directory
is called 'patches'). Then do "quilt push -a".

If you don't have quilt, apply the patches manually, in the order specified in the
'series' file, with a command like: "patch -p1 <patches/foo.patch"

2.6.32-rc5 patches

To apply, extract the patches and the series file. If you have 'quilt', extract
the file directly into the top level of the kernel source tree (the top directory
is called 'patches'). Then do "quilt push -a".

If you don't have quilt, apply the patches manually, in the order specified in the
'series' file, with a command like: "patch -p1 <patches/foo.patch"

2.6.31-rc1 patches

The following patches were submitted to the kernel mailing list in early July 2009.
There are patches against kernel version 2.6.31-rc1.

This tar archive contains a patches directory, with a series file and several patch
files. To use, extract at the source of your 2.6.29 kernel tree, and apply using
quilt with 'quilt push -a'.

Alternatively, apply the patches individually using 'patch -p1 <patches/p1.patch',
for each file listed in patches/series (in the order specified in the file).

This patch set was tested against a stock (mainline, from kernel.org) 2.6.29 kernel,
on an OMAP OSK development board (ARM-based, TI OMAP chip).

patches for gcc 4.4.0

Note recent ARM toolchains instrument the code with calls to '__gnu_mcount_nc' instead of 'mcount'.
If you get a compiler warning about missing the symbol '__gnu_mcount_nc', you should apply the
patch mentioned in this e-mail also: (http://marc.info/?l=linux-arm-kernel&m=124946219616111&w=2)

[Thanks to Jean Pihet of MontaVista for pointing this out]

Here is the above patch, and a patch which adds support for __gnu_mcount_nc to the
function_graph tracer.

History

Based on feeback from ftrace developers on the kernel mailing list, and from other
developers at the tracing mini-summit in Montreal, I started working on an updated duration
tracer, using a different filtering approach. This work was completed, and resulted
in a new trace, the "function_duration" tracer, being completed in September of 2009.

This work was described at ELC Europe and the Japan Linux Symposium, in October, 2009.
I was hoping to mainline the patches before the events, but ran out of time due to
bugs on my main testing platform.

Further Work

I need to try to mainline this feature. I'd like to get it into
Linux-tip or Linux-next sometime before the 2.6.33 merge window.

If you don't see it in mainline, just send me an e-mail asking about the status.