Open macdi opened 10 years ago
Hi Mehdi,
schedtool-dl is not yet updated to the very last changes to the ABI. Let me fix it in the next few days.
Thanks,
On Wed, 26 Feb 2014 09:58:30 -0800 macdi notifications@github.com wrote:
Hi Yuri,
I installed Linux-3.14.0-rc4 and I tried to test sched-deadline using schedtool as follow:
$> sudo ./schedtool -E -t 20000:100000:100000 -e yes
This results in this error:
Dumping mode: 0xa Dumping affinity: 0x0 We have 1 args to do Dump arg 0: yes setting PID 2224 to policy E: SCHED_DEADLINE, prio 0, runtime 20000, period 100000 ERROR: could not set PID 2224 to E: SCHED_DEADLINE - value out of range / policy not implemented
After looking at the schedtool source code, I found that sched-setattr(pid, p) returns -1.
Also I tried SCHED_FIFO, but I get a similar error:
$> ./schedtool -v -F -p 50 -e yes
Dumping mode: 0xb Dumping affinity: 0x0 We have 1 args to do Dump arg 0: yes setting PID 2693 to policy F: SCHED_FIFO, prio 50, runtime 0, period 0 policy = 1 ret = -1 ERROR: could not set PID 2693 to F: SCHED_FIFO - value out of range / policy not implemented
Could you please tell me what is wrong with my installation.
Thank u very much in advance.
Best regards, Mehdi
Reply to this email directly or view it on GitHub: https://github.com/jlelli/sched-deadline/issues/9
Hi, try it now :).
Best,
Hi Yuri,
I cloned the repository and I tried it, but I still have the same error.
This is the results of "git log" command:
~/dev/schedtool-dl$ git log
commit 834a0da49b1e1342d8724f590af67f7e6c7135f4 Author: Juri Lelli Date: Fri Jan 17 17:17:44 2014 +0100
adapt to tip/master ABI
commit 8b39f4654b871786d66835dbc607bbe9a684f466 Author: Juri Lelli Date: Thu Jan 16 17:48:57 2014 +0100
use sizeof instead of a define value
commit fb9c8c82254ad420e4582abdeed2b6dbf693edfa Author: Juri Lelli Date: Tue Dec 3 17:37:44 2013 +0100
New ABI
commit cd4e3f2f5a33c3266e25e447e8efbacb3b8c88da Author: Juri Lelli Date: Wed Feb 6 12:12:58 2013 -0800
syscall_magic: syscall numbers for V7
commit 96acd38aede7ca3852a86701a45b06a248f324d0 Author: Juri Lelli Date: Tue Nov 20 18:15:31 2012 -0800
Forward ported to sched-dl-V6
Do you have any idea? thank you very much.
best regards, Mehdi
Hi,
On Wed, 05 Mar 2014 01:55:38 -0800 macdi notifications@github.com wrote:
Hi Yuri,
I cloned the repository and I tried it, but I still have the same error.
Be sure to be on the right branch: https://github.com/jlelli/schedtool-dl/commits/master
You missed the very last commit: adapt to the very last changes to the ABI
Best,
This is the results of "git log" command:
~/dev/schedtool-dl$ git log
commit 834a0da49b1e1342d8724f590af67f7e6c7135f4 Author: Juri Lelli juri.lelli@gmail.com Date: Fri Jan 17 17:17:44 2014 +0100
adapt to tip/master ABI
commit 8b39f4654b871786d66835dbc607bbe9a684f466 Author: Juri Lelli juri.lelli@gmail.com Date: Thu Jan 16 17:48:57 2014 +0100
use sizeof instead of a define value
commit fb9c8c82254ad420e4582abdeed2b6dbf693edfa Author: Juri Lelli juri.lelli@gmail.com Date: Tue Dec 3 17:37:44 2013 +0100
New ABI
commit cd4e3f2f5a33c3266e25e447e8efbacb3b8c88da Author: Juri Lelli juri.lelli@gmail.com Date: Wed Feb 6 12:12:58 2013 -0800
syscall_magic: syscall numbers for V7
commit 96acd38aede7ca3852a86701a45b06a248f324d0 Author: Juri Lelli juri.lelli@gmail.com Date: Tue Nov 20 18:15:31 2012 -0800
Forward ported to sched-dl-V6
Do you have any idea? thank you very much.
best regards, Mehdi
Reply to this email directly or view it on GitHub: https://github.com/jlelli/sched-deadline/issues/9#issuecomment-36726148
Hi Yuri,
I updated the schedtool-dl sources and the new ABI is now working, thank you very much! But the test makes the CPU spinning non-stop, the only way to stop that is a reboot of the machine.
Do you have any idea of how could I correct this.
My test case is sudo ./schedtool -E -t 20000:100000:100000 -e yes
best regards, Mehdi
On Thu, 06 Mar 2014 02:39:43 -0800 macdi notifications@github.com wrote:
Hi Yuri,
I updated the schedtool-dl sources and the new ABI is now working, thank you very much! But the test makes the CPU spinning non-stop, the only way to stop that is a reboot of the machine.
Do you have any idea of how could I correct this.
My test case is sudo ./schedtool -E -t 20000:100000:100000 -e yes
This works here. Could you send me your CONFIG?
Thanks!
I also tried also this simple program, but does not worked too.
include
int main() { while(1) { printf("run...\n"); sleep(1);
} }best regards, Mehdi
Reply to this email directly or view it on GitHub: https://github.com/jlelli/sched-deadline/issues/9#issuecomment-36843398
Hi Yuri,
I installed Linux-3.14.0-rc4 and I tried to test sched-deadline using schedtool as follow:
$> sudo ./schedtool -E -t 20000:100000:100000 -e yes
This results in this error:
Dumping mode: 0xa Dumping affinity: 0x0 We have 1 args to do Dump arg 0: yes setting PID 2224 to policy E: SCHED_DEADLINE, prio 0, runtime 20000, period 100000 ERROR: could not set PID 2224 to E: SCHED_DEADLINE - value out of range / policy not implemented
After looking at the schedtool source code, I found that sched-setattr(pid, p) returns -1.
Also I tried SCHED_FIFO, but I get a similar error:
$> ./schedtool -v -F -p 50 -e yes
Dumping mode: 0xb Dumping affinity: 0x0 We have 1 args to do Dump arg 0: yes setting PID 2693 to policy F: SCHED_FIFO, prio 50, runtime 0, period 0 policy = 1 ret = -1 ERROR: could not set PID 2693 to F: SCHED_FIFO - value out of range / policy not implemented
Could you please tell me what is wrong with my installation.
Thank u very much in advance.
Best regards, Mehdi