Skip to contentSkip to conversation

possible bug in RP kernel

DISCUSSION Ingo Molnar 2 participants 3 messages Sep 12, 2005 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 8 lines · Florian Schmidt

Problem is: i wrote a small test program running at prio 80 that simply busy loops for about 15 seconds. It seems from the log output that the main thread never wakes up during the time of the test program running.

Sep 12 10:36:07 mango rt_watchdog: count 5
Sep 12 10:36:30 mango rt_watchdog: count 6
             ^^
Quoted 6 lines

23 seconds gap between two wakeups

Maybe my understanding of how sched fifo works is wrong, but i assumed a higher prio thread shold get woken up from a sleep by the scheduler which gets run by the timer interrupt [which is still non preemptible].

depending on what type of timeout you are using you'll also need to chrt the softirq-timer kernel thread(s) to prio 99. Otherwise the timer fn will have no chance to be executed. There's work going on by Thomas to make such things automatic, by prioritizing timers. If you have HRT enabled in the .config then it should mostly be automatic already though.

Ingo

#2 lore raw
Quoted 7 lines · On Mon, 12 Sep 2005 11:01:15 +0200 Ingo Molnar <[email protected]> wrote:
Quoted 6 lines

23 seconds gap between two wakeups

Maybe my understanding of how sched fifo works is wrong, but i assumed a higher prio thread shold get woken up from a sleep by the scheduler which gets run by the timer interrupt [which is still non preemptible].

Quoted 6 lines

depending on what type of timeout you are using you'll also need to chrt the softirq-timer kernel thread(s) to prio 99. Otherwise the timer fn will have no chance to be executed. There's work going on by Thomas to make such things automatic, by prioritizing timers. If you have HRT enabled in the .config then it should mostly be automatic already though.

Ah,

thanks for the info. So it is a user (me) bug in the end :) This has helped. Actually the code i had attached had another bug in it. But that wasn't the responsible one.

Thanks again, and sorry for the multiple mails,
Florian Schmidt

Signature · 2 lines
Palimm Palimm!
http://tapas.affenbande.org
#3 lore raw
Quoted 17 lines · Florian Schmidt
Quoted 7 lines · On Mon, 12 Sep 2005 11:01:15 +0200 Ingo Molnar <[email protected]> wrote:
Quoted 6 lines

23 seconds gap between two wakeups

Maybe my understanding of how sched fifo works is wrong, but i assumed a higher prio thread shold get woken up from a sleep by the scheduler which gets run by the timer interrupt [which is still non preemptible].

Quoted 6 lines

depending on what type of timeout you are using you'll also need to chrt the softirq-timer kernel thread(s) to prio 99. Otherwise the timer fn will have no chance to be executed. There's work going on by Thomas to make such things automatic, by prioritizing timers. If you have HRT enabled in the .config then it should mostly be automatic already though.

Quoted 5 lines

Ah,

thanks for the info. So it is a user (me) bug in the end :) This has helped. Actually the code i had attached had another bug in it. But that wasn't the responsible one.

well, it's not really your 'bug' - the priority setup isnt very intuitive at the moment, and the goal is to automate as much of it as possible. The way various system threads interact is highly implementation dependent, and you shouldnt really be required to know about softirq-timer. We'll try to simplify these things as much as possible.

Ingo