Re: allowed_cpus issue in rt_task_init_schmod call
Emmanuel Pacaud <[email protected]>
| Newsgroups | gmane.linux.real-time.rtai |
|---|---|
| Message-ID | <[email protected]> |
Le mar. 8 mars 2016 à 16:48, Paolo Mantegazza <[email protected]> a écrit : > How did you check it? Using "cat /rtai/sched"? No, with top. But the result is the same with /proc/rtai/scheduler [pacaud@lappc-f587:~/virgo/TolmBase/v5r7/cmt]$ ../$UNAME/RtaiTaskInitTest.exe& [1] 4547 [pacaud@lappc-f587:~/virgo/TolmBase/v5r7/cmt]$ ../$UNAME/RtaiTaskInitTest.exe & [2] 4548 [pacaud@lappc-f587:~/virgo/TolmBase/v5r7/cmt]$ ../$UNAME/RtaiTaskInitTest.exe & [3] 4549 [pacaud@lappc-f587:~/virgo/TolmBase/v5r7/cmt]$ ../$UNAME/RtaiTaskInitTest.exe & [4] 4550 using: rt_task_init_schmod (rt_get_name (0), 10, 0, 0, SCHED_FIFO, 3); gives: Priority Period(ns) FPU Sig State CPU Task HD/SF PID RT_TASK * TIME ------------------------------------------------------------------------------ 1000000000 0 Yes No 0x3 0:1 1 0 4533 ffffc900106c0230 0 1000000010 0 Yes No 0x0 0:1 2 0 4550 ffffc900106c4230 0 TIMED READY 1000000010 0 Yes No 0x0 1:2 3 0 4547 ffffc900106c1230 0 TIMED READY 1000000010 0 Yes No 0x0 2:4 4 0 4548 ffffc900106c2230 0 TIMED READY 1000000010 0 Yes No 0x0 3:8 5 0 4549 ffffc900106c3230 0 TIMED READY > Clearly it may be a long time standing and undetected bug. > I've not 4 core handy, so can you check if it works when you force > your task onto a single CPU (1, 2, 4, 8)? Yes, it works in this case. Cheers, Emmanuel. _______________________________________________ Rtai mailing list [email protected] https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai