[lkml]   [2005]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] Real-Time Preemption, -RT-2.6.11-rc3-V0.7.38-01
What is the proper way to setup a real counting semaphore under the
-RT kernel?

I've noticed that just using a struct semaphore, normal counting
semaphore usage[*] can trigger the "lock recursion deadlock" in
kernel/rt.c since 'struct semaphore' now uses an rt_mutex.

What I've done for now is to use sema_init_nocheck() to disable the
checking in the case of a counting semaphore, but I remember seeing
discussion in an earlier thread about creating a separate counting
semaphore type. Is this still planned?


[*] For example, an open semaphore being down'ed and thus acquired and
the same thread doing a down() again before another thread has a
chance to up() the semaphore.

Ingo Molnar <> writes:

> i have released the -V0.7.38-01 Real-Time Preemption patch, which can be
> downloaded from the usual place:
> Changes since -37-03:
> - merged to 2.6.11-rc3
> - deadlock-tracer fix from Eugeny S. Mints
> - converted an oprofile spinlock to raw, which should fix the bug
> reported by Peter Zijlstra.
> to create a -V0.7.38-01 tree from scratch, the patching order is:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:10    [W:0.156 / U:2.292 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site