OProfile 0.5.1 has been released. OProfile is still in alpha,
but has been proven stable for many users.

Release notes
-------------

For 2.2 kernels, the module must be compiled as the same user
that owns the kernel source tree.
 
nosmp is not supported in kernels before 2.4.10 (bug #463087).

The pre-emptable kernel option is not supported in 2.4 (bug #478516).
 
Power management on laptops can be incompatible with OProfile in 2.4 (bug #554927).

The utilities op_start, op_stop, op_dump, and op_session are deprecated. They
are still available in this release, but it is recommended that the opcontrol
script is used instead, as they will be removed.

New features
------------

x86-64 support for 2.4 kernels has been enabled in this release.

Kernel profiles can now be separated on a per-application basis. This means you
can see where an application spent its time in the kernel. Note that currently,
hardware interrupts are credited to applications instead of the kernel itself under
some circumstances, as described in the documentation.

The oprof_start GUI now works with 2.5 kernels.

oprofpp -s symbol_name can now look up symbol names in dependent shared libraries
for the application when using --show-shared-libs.

A new smart demangler has been added, enabled by the -D option. This improves the
readability of symbols generated by the C++ standard library.

Bug fixes
---------

oprofpp -s symbol crash fixed (bug #686272).

A daemon crash when using initrd modules has been fixed (bug #686175).

The opcontrol script is better at detecting stale lock files from
daemon crashes (or kill -9).

Formatting of VMAs in summaries is now better with 64-bit addresses.

A unit mask problem with AMD's SEG_REG_RELOAD event has been fixed.

opcontrol now supports --rtc-value, --kernel-only, and --note-table-size.

opcontrol --deinit works better. opcontrol error handling has been improved.

A remaining 64-bit problem has been fixed.