Searched refs:reschedule (Results 1 – 16 of 16) sorted by relevance
| /Zephyr-Core-3.7.0/doc/develop/api/ |
| D | terminology.rst | 11 if executing the function reaches a reschedule point
37 reschedule section in API Terminology
40 The reschedule attribute is used on a function that can reach a
41 :ref:`reschedule point <scheduling_v2>` within its execution.
50 reschedule point and the relative priorities of the invoking thread and argument
53 Note that in the case of timeslicing, or reschedule points executed from
56 Functions that are not **reschedule** may be invoked from either thread
59 Functions that are **reschedule** may be invoked from thread context.
61 Functions that are **reschedule** but not **sleep** may be invoked from
77 will not replace a running cooperative-only thread at a reschedule point
[all …]
|
| /Zephyr-Core-3.7.0/soc/st/stm32/stm32wbax/hci_if/ |
| D | linklayer_plat.c | 139 ARM_IRQ_DIRECT_DYNAMIC_CONNECT(RADIO_INTR_NUM, 0, 0, reschedule); in link_layer_register_isr()
149 ARM_IRQ_DIRECT_DYNAMIC_CONNECT(RADIO_SW_LOW_INTR_NUM, 0, 0, reschedule); in link_layer_register_isr()
|
| /Zephyr-Core-3.7.0/subsys/net/lib/trickle/ |
| D | trickle.c | 88 static inline void reschedule(struct net_trickle *trickle) in reschedule() function
119 reschedule(trickle); in interval_timeout()
|
| /Zephyr-Core-3.7.0/arch/mips/core/ |
| D | isr.S | 161 j reschedule
211 reschedule: label
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 42 additional time remaining. If the latter, reschedule the callback.
|
| /Zephyr-Core-3.7.0/arch/riscv/core/ |
| D | isr.S | 432 j reschedule
679 reschedule: label
|
| /Zephyr-Core-3.7.0/kernel/ |
| D | pipes.c | 327 sys_dlist_t *dest_list, bool *reschedule) in pipe_write() argument
365 *reschedule = true; in pipe_write()
|
| D | work.c | 1040 SYS_PORT_TRACING_OBJ_FUNC_ENTER(k_work, reschedule, dwork, delay); in k_work_reschedule()
1044 SYS_PORT_TRACING_OBJ_FUNC_EXIT(k_work, reschedule, dwork, delay, ret); in k_work_reschedule()
|
| D | Kconfig.smp | 93 set of CPUs that need an IPI to trigger a reschedule in response to
|
| /Zephyr-Core-3.7.0/doc/kernel/services/scheduling/ |
| D | index.rst | 17 are called **reschedule points**. Some potential reschedule points are:
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/mesh/ |
| D | transport.c | 932 goto reschedule; in trans_ack()
946 reschedule: in trans_ack()
|
| /Zephyr-Core-3.7.0/doc/kernel/services/smp/ |
| D | smp.rst | 233 sufficient to trigger a reschedule on the N CPUs that results with them
|
| /Zephyr-Core-3.7.0/doc/kernel/services/ |
| D | interrupts.rst | 154 occur. Thread B will not run until the next :ref:`reschedule point
|
| /Zephyr-Core-3.7.0/doc/releases/ |
| D | release-notes-3.4.rst | 488 * Modified the ticker implementation to reschedule unreserved tickers that use
|
| D | release-notes-2.2.rst | 1068 * :github:`20802` - reschedule not done after mutex unlock
|
| /Zephyr-Core-3.7.0/doc/ |
| D | zephyr.doxyfile.in | 283 …"reschedule=\htmlonly reschedule \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_r…
|
