Lines Matching +full:waking +full:- +full:up

6 programs - the BPF scheduler.
19   `SysRq-S`.
24   `sched_ext_dump` tracepoint. The SysRq key sequence `SysRq-D`
35 .. code-block:: none
54 in ``ops->flags``, all ``SCHED_NORMAL``, ``SCHED_BATCH``, ``SCHED_IDLE``, and
58 set in ``ops->flags``, only tasks with the ``SCHED_EXT`` policy are scheduled
62 Terminating the sched_ext scheduler program, triggering `SysRq-S`, or
66 .. code-block:: none
68     # make -j16 -C tools/sched_ext
79 .. code-block:: none
90 .. code-block:: none
98 .. code-block:: none
112 .. code-block:: none
126 .. code-block:: c
182             exit_type = ei->type;
195 ---------------
205 DSQ. A task in a non-local DSQ is "move"d into the target CPU's local DSQ.
213 ----------------
215 The following briefly shows how a waking task is scheduled and executed.
217 1. When a task is waking up, ``ops.select_cpu()`` is the first operation
219    hint. Second, waking up the selected CPU if idle.
226    A side-effect of selecting a CPU is waking it up from idle. While a BPF
227    scheduler can wake up any cpu using the ``scx_bpf_kick_cpu()`` helper,
259      used - ``SCX_DSQ_LOCAL``, ``SCX_DSQ_LOCAL_ON | cpu``,
263      rather than performing them immediately. There can be up to
266    * ``scx_bpf_move_to_local()`` moves a task from the specified non-local
285 built-in DSQs are used, there is no need to implement ``ops.dispatch()`` as
291 ``SCX_DSQ_LOCAL`` and ``SCX_DSQ_GLOBAL`` do not support priority-queue
297 --------------
299 The following pseudo-code summarizes the entire lifecycle of a task managed
302 .. code-block:: c
347   * ``scx_qmap[.bpf].c``: A multi-level FIFO scheduler supporting five