lkml.org 
[lkml]   [2011]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: CONFIG_PEEMPT_RT_FULL vs. CONFIG_PREEMPT_RTB
From
Hi,

> Besides of the cpu load i also found out that with rt11 i can again wake up
> usermode from a IRQF_NO_THREAD waiting on a waitqueue. So the steps outlined
> in this mail http://www.spinics.net/lists/linux-rt-users/msg06834.html do not
> seem to be neccessary anymore? Or does this create an error and than some high
> load?

Try running with CONFIG_DEBUG_SPINLOCK_SLEEP and you would probably
see some errors...

If you have CONFIG_PREEMPT_RT_FULL set, then the __wake_up function of
the waitqueue runs into a spinlock. This spinlock will be converted to
a mutex since it is a regular spinlock, not a raw_spinlock. A
mutex-lock might sleep. Calling sleeping functions from hard-irq
context is illegal.

Kind regards,

Remy


\
 
 \ /
  Last update: 2011-08-15 22:47    [W:0.053 / U:0.364 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site