>>> Ingo Molnar <[email protected]> 29.09.06 20:39 >>>
>* Andi Kleen <[email protected]> wrote:
>> "Jan Beulich" <[email protected]> writes:
>> > There's nothing stack trace/unwind related among the functions listed at all afaics.
>> > I don't know much about how profiling works, is it perhaps just missing something?
>> Perhaps lockdep calls them with interrupts off? The old profiler
>> doesn't support profiling with interrupts off. oprofile does, but it
>> cannot be used at early boot.
>Yes, lockdep does everything that changes the dependency graph(s) with
>irqs off. Jan, i bounced you the mail with the function traces included,
>that should show you the overhead points.
Okay, makes sense then. I'll get to addressing the (already identified) cause
as soon as I can.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]