I think that is an idle task.
However, for the second half of the analysis, the ciritcal task is being preempted by swapperswapper, the idle task, from "Ubuntu".
This state is reached when the QEMU thread emulating a vCPU is scheduled out of a pCPU, and if no thread other than the idle idle task is scheduled to run on this vCPU in the guest OS (transition 4).
On Linux, the purpose of swapper swapper (the idle idle task) is to invoke the scheduler to choose potential threads ready for execution, or to halt the CPU in case no thread is ready to run.
When an idle task slot requires a Reduce job, search in L d orderly for a task whose Map jobs have all finished and then select a Reduce job of the selected task.
Secondly, in the guest operating system, the CPU associated with the specified QEMU thread must be in the running state as well, meaning that any process other than the idle task (swapperswapper) is executing on the CPU.
As highlighted, recognizing the different parts of the workflow is easy: as long as the DSPs are in the "idle" task, they are waiting for their master's input.
Map: When an idle task slot requires a Map job, select a Map job of the first task in sequence S. When all Map jobs of the first task in S are allocated, remove the first task from S. Reduce: Sort the tasks in JS increasingly according to their times to finish and then get a sorted queue ( {L}_a=left{{j}_1^{prime },{j}_2^{prime },dots, {j}_{left|JSright|}^{prime}right} ).
1. Design four different experimental tasks: idling task, gazing task, motion imagery task, and motion task.
or keep idle; other tasks cannot hold this resource at the same time.
