System, method and program product for determining execution flow of the scheduler in response to setting a scheduler control variable by the debugger or by a processing entity
View Patent ↗A system, computer program and a method for debugging a system, the method includes: controlling, by a debugger, an execution flow of a processing entity; setting, by the debugger or the processing entity, a value of a scheduler control variable accessible by the scheduler; wherein the debugger is prevented from directly controlling an execution flow of a scheduler; and determining, by the scheduler, an execution flow of the scheduler in response to a value of the scheduler control variable.
1. A method for debugging a system, the method comprises:
checking if a scheduler status variable indicates a scheduler is in a normal mode, such that the scheduler status variable indicates that the scheduler, in the normal mode, executes at least one scheduling iteration;
updating, during each of a plurality of scheduling iterations in the normal mode, a queue starvation watermark value of each of a plurality of task data structures that is not eligible to move to a running tasks queue, until a first queue starvation watermark value of a first task data structure of the plurality of the task data structures reaches a queue starvation watermark threshold;
generating a task starvation indication if during an additional number of additional scheduling iterations, the first task data structure is still prevented from being moved to the running tasks queue, wherein the additional number is responsive to a task starvation watermark;
freezing sorted tasks queues that do not store the first task data structure or otherwise ignoring the task data structures stored in other sorted tasks queues during the additional number of the scheduling iterations;
controlling, by a debugger, a processing entity execution flow of a processing entity;
setting, by the debugger or the processing entity, a value of a scheduler control variable accessible by the scheduler, wherein the debugger can set the value of the scheduler control variable and the processing entity can set the value of the scheduler control variable; and
determining, by the scheduler, the scheduler execution flow of the scheduler in response to the setting the value of the scheduler control variable;
checking if the scheduler status variable indicates the scheduler is not in the normal mode; and
performing, by the debugger, a debugging operation in response to the scheduler status variable indicating that the scheduler is not in the normal mode.
2. The method according to claim 1 comprising setting, by the scheduler, a value of the scheduler status variable.
3. The method according to claim 1 comprising checking, by the scheduler, the value of the scheduler control variable before each of the at least one scheduling iteration.
4. The method according to claim 1 wherein the controlling, by the debugger, the processing entity execution flow of the processing entity comprises controlling the processing entity execution flow of multiple processing entities by the debugger, wherein the multiple processing entities comprise the processing entity.
5. The method according to claim 1 comprising stopping the processing entity execution flow of multiple processing entities by utilizing Joint Test Access Group (JTAG) interfaces of the multiple processing entities, wherein the multiple processing entities comprise the processing entity.
6. The method according to claim 1 comprising requesting, by the debugger, the processing entity to control an other processing entities execution flow of other processing entities.
7. The method according to claim 1 wherein the processing entity is a core and wherein the scheduler is a multiple-purpose entity that is disabled from performing a non-scheduler task during the scheduling of a processing entity task.
8. A system having debugging capabilities, the system comprises:
a processing entity;
a debugger that is adapted to control a processing entity execution flow of the processing entity;
a scheduler;
wherein either one of the debugger or the processing entity is adapted to check if a scheduler status variable indicates that the scheduler is in a normal mode, such that the scheduler status variable indicates that the scheduler, in the normal mode, executes at least one scheduling iteration, to update a value of a scheduler control variable accessible by the scheduler, to check if a scheduler status variable indicates that the scheduler is not in the normal mode, and to perform a debugging operation, wherein the debugger can update the value of the scheduler control variable and the processing entity can update the value of the scheduler control variable; and
wherein the scheduler is adapted to determine the scheduler execution flow of the scheduler in response to the value of the scheduler control variable, wherein the system is further adapted to update, during each of a plurality of scheduling iterations, a queue starvation watermark value of each of a plurality of task data structures that is not eligible to move to a running tasks queue, until a first queue starvation watermark value of a first task data structure of the plurality of the task data structures reaches a queue starvation watermark threshold, to generate a task starvation indication if during an additional number of additional scheduling iterations, the first task data structure is still prevented from being moved to the running tasks queue, wherein the additional number is responsive to a task starvation watermark, and to freeze sorted tasks queues that do not store the first task data structure or otherwise ignoring the task data structures stored in other sorted tasks queues during the additional number of the scheduling iterations.
9. The system according to claim 8 wherein the scheduler is adapted to set a value of the scheduler status variable.
10. The system according to claim 8 wherein the scheduler is adapted to check the value of the scheduler control variable before each of the at least one scheduling iteration.
11. The system according to claim 8 wherein the debugger is adapted to control the processing entity execution flow of multiple processing entities, wherein the multiple processing entities comprise the processing entity.
12. The system according to claim 8 wherein the debugger is adapted to stop the processing entity execution flow of multiple processing entities by utilizing JTAG interfaces of the multiple processing entities, wherein the multiple processing entities comprise the processing entity.
13. The system according to claim 8 wherein the debugger is adapted to request, the processing entity to control an other processing entities execution flow of other processing entities.
14. The system according to claim 8 wherein the processing entity is a core and wherein the scheduler is multiple-purpose entity that is disabled from performing a non-scheduler task during the scheduling of a processing entity task.
15. A computer program product that comprises a non-transitory computer readable medium that stores instructions that when executed perform the steps comprising:
checking if a scheduler status variable indicates a scheduler is in a normal mode, such that the scheduler status variable indicates that the scheduler, in the normal mode, executes at least one scheduling iteration;
updating, during each of a plurality of scheduling iterations in the normal mode, a queue starvation watermark value of each of a plurality of task data structures that is not eligible to move to a running tasks queue, until a first queue starvation watermark value of a first task data structure of the plurality of the task data structures reaches a queue starvation watermark threshold;
generating a task starvation indication if during an additional number of additional scheduling iterations, the first task data structure is still prevented from being moved to the running tasks queue, wherein the additional number is responsive to a task starvation watermark;
freezing sorted tasks queues that do not store the first task data structure or otherwise ignoring the task data structures stored in other sorted tasks queues during the additional number of the scheduling iterations;
controlling, by a debugger, a processing entity execution flow of a processing entity;
setting, by the debugger or the processing entity, a value of a scheduler control variable accessible by the scheduler, wherein the debugger can set the value of the scheduler control variable and the processing entity can set the value of the scheduler control variable; and
determining, by the scheduler, the scheduler execution flow of the scheduler in response to the setting the value of the scheduler control variable;
checking if the scheduler status variable indicates the scheduler is not in the normal mode; and
performing a debugging operation.
16. The computer program product according to claim 15 comprising instructions, that when executed perform setting, by the scheduler, a value of the scheduler status variable.
17. The computer program product according to claim 15 comprising instructions, that when executed perform checking, by the scheduler, the value of the scheduler control variable before each of the at least one scheduling iteration.
18. The computer program product according to claim 15 comprising instructions, that when executed perform controlling the processing entity execution flow of multiple processing entities by the debugger, wherein the multiple processing entities comprise the processing entity.