> >> 222609 BKL 1 712/tty_io.c 697/sched.c
> I don't quite understand how locked region can start in
> 712/tty_io.c and end in 697/sched.c?
The BKL is dropped whenever the task voluntarily blocks in the kernel.
This is what you are seeing reported here. It will be reacquired when
the task is rescheduled:
> This is strange too:
> >> 152903 spin_lock 5 547/sched.c 714/tty_io.c
> spinlock? Unlocked by unlock_kernel()???
The latency measuring code isn't always accurate in reporting the cause
in this case: if it's unlocked by unlock_kernel and locked in sched.c,
then it's the reacqusition of the BKL by a task that was blocked while
holding the lock.
Nigel Gamble nigel@nrg.org
Mountain View, CA, USA. http://www.nrg.org/
-
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/