Skip to contentSkip to conversation

2.6.15-rt3 + Open Posix Test Suite

DISCUSSION Daniel Walker 2 participants 3 messages Jan 10, 2006 – Jan 11, 2006

lore
Share & tools
lore
#0 lore raw

It's worth noting that a few tests in the current Open Posix Test Suite
hang RT systems.

Specifically this test (hope this url comes through),

http://cvs.sourceforge.net/viewcvs.py/*checkout*/posixtest/posixtestsuite/conformance/interfaces/sched_setparam/10-1.c?rev=1.2

sched_setparam test 10-1.c and I think 9-1.c .

The 10-1 test spawns some children at SCHED_FIFO priority 99 , then runs the following,

void child_process(){
	alarm(2);

	while(1) {
		(*shmptr)++;
		sched_yield();
	}
}

I'm sure this is what's hanging the system, the yield() is one issue. Another is why the alarm() is never delivered .

Daniel

#1 lore raw
Quoted 21 lines · Daniel Walker

It's worth noting that a few tests in the current Open Posix Test Suite
hang RT systems.

Specifically this test (hope this url comes through),

http://cvs.sourceforge.net/viewcvs.py/*checkout*/posixtest/posixtestsuite/conformance/interfaces/sched_setparam/10-1.c?rev=1.2

sched_setparam test 10-1.c and I think 9-1.c .

The 10-1 test spawns some children at SCHED_FIFO priority 99 , then runs the following,

void child_process(){
	alarm(2);

	while(1) {
		(*shmptr)++;
		sched_yield();
	}
}
Quoted 2 lines

I'm sure this is what's hanging the system, the yield() is one issue. Another is why the alarm() is never delivered .

This runs a while loop at SCHED_FIFO prio 99? And alarm never happens. Doesn't the alarm get activated by the softirqd that is running at a lower priority? Seems that this is starving out the softirq from getting the alarm.

I believe that Thomas once had priorities attached to the timers. I'd like to see that again, and may even start adding them myself, such that when a process activates a timer, when that timer goes off, the softirq will get the priority of the timer. But this has some complications to be sorted out.

-- Steve

#2 lore raw
Quoted 5 lines · Steven Rostedt

This runs a while loop at SCHED_FIFO prio 99? And alarm never happens. Doesn't the alarm get activated by the softirqd that is running at a lower priority? Seems that this is starving out the softirq from getting the alarm.

I thought alarm was a signal (SIGALRM) ? If it's delivered by softirqd then this makes sense. Your right , it's softirqd related.

The processes also calls yield() inside it's while loop . We have warnings about yield() and RT tasks.

Quoted 5 lines

I believe that Thomas once had priorities attached to the timers. I'd like to see that again, and may even start adding them myself, such that when a process activates a timer, when that timer goes off, the softirq will get the priority of the timer. But this has some complications to be sorted out.

Yes, I remember . Do we fix the test in this case, or the kernel ?

Daniel