On Sat, 2011-07-30 at 09:12 +0200, Mike Galbraith wrote:
> y profile looks much better, but jitter proggy using posix-timers on 56
> cores warms up a spot you know all about. Lucky me, I know where fixes
> for that bugger live.
JiitterChasing::TheEnd() doesn't exist does it? Aw poo.
30999 0.05% [k] lock_timer
31000 |
31001 --- do_schedule_next_timer
31002 dequeue_signal
31003 |
31004 |--87.94%-- sys_rt_sigtimedwait
31005 | system_call_fastpath
31006 | |
31007 | |--20.24%-- 0x7f0935011f27
31008 | | do_sigwait
# dso: [kernel.kallsyms]
# Events: 118K cycles
#
# Overhead Symbol
# ........ ...................................
#
22.82% [k] _raw_spin_lock_irqsave
|
|--32.46%-- rt_mutex_trylock
| tty_write_lock
| tty_write
| vfs_write
| sys_write
| system_call_fastpath
| |
| |--4.38%-- 0x7f46672a30f0
| | __GI___libc_write
...
|
|--32.20%-- rt_mutex_slowlock
| tty_write_lock
| tty_write
| vfs_write
| sys_write
| system_call_fastpath
| |
| |--4.71%-- 0x7f46672a30f0
| | __GI___libc_write
...
|--25.36%-- rcu_sched_qs
| __schedule
| |
| |--52.52%-- preempt_schedule
| | try_to_wake_up
| | signal_wake_up
| | send_sigqueue
| | posix_timer_event
| | posix_timer_fn
| | run_hrtimer_softirq
| | run_ksoftirqd
| | kthread
| | kernel_thread_helper
| |
| --47.48%-- schedule
| rt_spin_lock_slowlock
| lock_timer
| do_schedule_next_timer
| dequeue_signal
| |
| |--63.61%-- sys_rt_sigtimedwait
| | system_call_fastpath
| | |
| | |--9.26%-- 0x7f3c840acf27
| | | do_sigwait
...
| | | do_sigwait
| | --5.58%-- [...]
| |
| --36.39%-- get_signal_to_deliver
| do_signal
| do_notify_resume
| int_signal
| |
| |--6.17%-- 0x7f1dd90610f0
| | __GI___libc_write
...
|
|--6.54%-- rt_mutex_slowunlock
| tty_write_unlock
| tty_write
| vfs_write
| sys_write
| system_call_fastpath
| |
| |--6.06%-- 0x7f11267610f0
| | __GI___libc_write
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
