lkml.org 
[lkml]   [2007]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: preemption and rwsems (was: Re: missing madvise functionality)

* David Howells <dhowells@redhat.com> wrote:

> But short of recording the lock sequence, I don't think there's anyway
> to find out for sure. printk probably won't cut it as a recording
> mechanism because its overheads are too great.

getting a good trace of it is easy: pick up the latest -rt kernel from:

http://redhat.com/~mingo/realtime-preempt/

enable EVENT_TRACING in that kernel, run the workload
and do:

scripts/trace-it > to-ingo.txt

and send me the output. It will be large but interesting. That should
get us a whole lot closer to what happens. A (much!) more finegrained
result would be to also enable FUNCTION_TRACING and to do:

echo 1 > /proc/sys/kernel/mcount_enabled

before running trace-it.

Ingo

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-04-05 21:15    [W:0.235 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site