updates for oprofile
Ingo,
please pull oprofile updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core
You might want to pull from 'for-next' instead that includes an additional merge with tip/tracing/core to resolve conflicts with that branch.
Thanks.
-Robert
--
commit b971f06187d83b5c03d2b597cccdfef421c0ca91
Merge: cb6e943 c1ab9ca
Author: Robert Richter <[email protected]>
Date: Fri Apr 23 16:47:51 2010 +0200
Merge commit 'tip/tracing/core' into oprofile/core
Conflicts:
drivers/oprofile/cpu_buffer.c
commit cb6e943ccf19ab6d3189147e9d625a992e016084
Author: Andi Kleen <[email protected]> Date: Thu Apr 1 03:17:25 2010 +0200
oprofile: remove double ring buffering
oprofile used a double buffer scheme for its cpu event buffer to avoid races on reading with the old locked ring buffer.
But that is obsolete now with the new ring buffer, so simply use a single buffer. This greatly simplifies the code and avoids a lot of sample drops on large runs, especially with call graph.
Based on suggestions from Steven Rostedt
For stable kernels from v2.6.32, but not earlier.
commit a36bf32e9e8a86f291f746b7f8292e042ee04a46
Merge: bc078e4 01bf0b6
Author: Robert Richter <[email protected]>
Date: Fri Apr 23 14:30:22 2010 +0200
Merge commit 'v2.6.34-rc5' into oprofile/core
commit bc078e4eab65f11bbaeed380593ab8151b30d703
Author: Martin Schwidefsky <[email protected]> Date: Tue Mar 2 16:01:10 2010 +0100
oprofile: convert oprofile from timer_hook to hrtimer
Oprofile is currently broken on systems running with NOHZ enabled. A maximum of 1 tick is accounted via the timer_hook if a cpu sleeps for a longer period of time. This does bad things to the percentages in the profiler output. To solve this problem convert oprofile to use a restarting hrtimer instead of the timer_hook.
Signature · 3 lines
Advanced Micro Devices, Inc. Operating System Research Center email: [email protected]
Quoted 9 lines · Robert Richter
Ingo,
please pull oprofile updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.gitcoreYou might want to pull from 'for-next' instead that includes an additional merge with tip/tracing/core to resolve conflicts with that branch.
Pulled, thanks Robert!
Ingo