/Zephyr-latest/tests/unit/net_timeout/ |
D | main.c | 22 uint64_t deadline = nto->timer_start; 25 deadline += remaining; 30 remaining, deadline); 200 uint64_t deadline; in ZTEST() local 210 deadline = net_timeout_deadline(&nto, now); in ZTEST() 223 zassert_equal(net_timeout_deadline(&nto, now), deadline, in ZTEST() 238 zassert_equal(net_timeout_deadline(&nto, now), deadline, in ZTEST() 253 zassert_equal(net_timeout_deadline(&nto, now), deadline, in ZTEST() 269 zassert_equal(net_timeout_deadline(&nto, now), deadline, in ZTEST() 287 zassert_equal(net_timeout_deadline(&nto, now), deadline, in ZTEST() [all …]
|
/Zephyr-latest/subsys/net/lib/sntp/ |
D | sntp_simple.c | 17 uint64_t deadline; in sntp_simple_helper() local 27 deadline = (uint64_t)timeout; in sntp_simple_helper() 29 deadline = k_uptime_get() + (uint64_t)timeout; in sntp_simple_helper() 36 while (k_uptime_get() < deadline) { in sntp_simple_helper()
|
/Zephyr-latest/lib/os/ |
D | p4wq.c | 23 th->base.prio_deadline = item->deadline; in set_prio() 35 if (aw->deadline != bw->deadline) { in rb_lessthan() 36 return aw->deadline - bw->deadline > 0; in rb_lessthan() 67 (a->deadline != b->deadline)) { in item_lessthan() 68 return a->deadline - b->deadline > 0; in item_lessthan() 223 item->deadline += k_cycle_get_32(); in k_p4wq_submit()
|
/Zephyr-latest/subsys/net/ip/ |
D | net_timeout.c | 48 uint64_t deadline; in net_timeout_deadline() local 57 deadline = start + timeout->timer_timeout; in net_timeout_deadline() 58 deadline += (uint64_t)NET_TIMEOUT_MAX_VALUE in net_timeout_deadline() 61 return (int64_t)deadline; in net_timeout_deadline()
|
/Zephyr-latest/drivers/timer/ |
D | apic_tsc.c | 112 static void set_trigger(uint64_t deadline) in set_trigger() argument 115 wrmsr(IA32_TSC_DEADLINE_MSR, deadline); in set_trigger() 119 uint64_t delta_cycles = deadline - MIN(deadline, curr_cycle); in set_trigger()
|
D | Kconfig.x86 | 39 bool "Local APIC timer using TSC deadline mode" 45 deadline capability. The use of a free-running 64 bit 52 deadline capability. 61 If your CPU supports invariant TSC but no TSC deadline capability
|
/Zephyr-latest/tests/kernel/sched/deadline/ |
D | CMakeLists.txt | 5 project(deadline) project
|
/Zephyr-latest/tests/lib/p4workq/src/ |
D | main.c | 44 item->item.deadline = sys_rand32_get() % k_ms_to_cyc_ceil32(2); in stress_sub() 156 item->deadline = k_us_to_cyc_ceil32(100); in add_new_item() 260 simple_item.deadline = 0; in ZTEST()
|
/Zephyr-latest/subsys/rtio/ |
D | rtio_workq.c | 77 work->deadline = 0; in rtio_work_req_submit()
|
/Zephyr-latest/kernel/ |
D | sched.c | 1012 void z_impl_k_thread_deadline_set(k_tid_t tid, int deadline) in z_impl_k_thread_deadline_set() argument 1015 deadline = CLAMP(deadline, 0, INT_MAX); in z_impl_k_thread_deadline_set() 1018 int32_t newdl = k_cycle_get_32() + deadline; in z_impl_k_thread_deadline_set() 1038 static inline void z_vrfy_k_thread_deadline_set(k_tid_t tid, int deadline) in z_vrfy_k_thread_deadline_set() argument 1043 K_OOPS(K_SYSCALL_VERIFY_MSG(deadline > 0, in z_vrfy_k_thread_deadline_set() 1045 (int)deadline)); in z_vrfy_k_thread_deadline_set() 1047 z_impl_k_thread_deadline_set((k_tid_t)thread, deadline); in z_vrfy_k_thread_deadline_set()
|
D | Kconfig | 113 bool "Earliest-deadline-first scheduling" 115 This enables a simple "earliest deadline first" scheduling 116 mode where threads can set "deadline" deltas measured in 118 single priority will choose the next expiring deadline and 345 features like deadline scheduling that need to sort threads
|
/Zephyr-latest/include/zephyr/sys/ |
D | p4wq.h | 32 int32_t deadline; member
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_timeout.rst | 54 deadline of the timeout. This exists primarily for testing but may have use
|
/Zephyr-latest/doc/kernel/services/scheduling/ |
D | index.rst | 43 However, when both earliest-deadline-first scheduling is enabled 45 static priority, then the thread with the earlier deadline is considered 46 to have the higher priority. Thus, when earliest-deadline-first scheduling is 49 :c:func:`k_thread_deadline_set` is used to set a thread's deadline. 93 features make it incompatible with features like deadline scheduling that
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | workqueue.rst | 49 specifically allowing a previous deadline to remain unchanged when a work 262 delayable items, but if the queue is plugged and the deadline expires the 345 deadline should be extended if a new event occurs. An example is collecting 356 unconditionally sets the deadline for the work, replacing any previous 465 the deadline. 515 (for delayable work) if the deadline has completed but the work is still in
|
/Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/ |
D | ec_host_cmd_backend_spi_stm32.c | 615 int64_t deadline = k_ticks_to_us_floor64(k_uptime_ticks()) + EC_SPI_CMD_RX_TIMEOUT_US; in wait_for_rx_bytes() local 643 if (current_time >= deadline) { in wait_for_rx_bytes()
|
/Zephyr-latest/subsys/net/lib/dhcpv4/ |
D | dhcpv4.c | 416 int64_t deadline = start + MSEC_PER_SEC * time; in dhcpv4_get_timeleft() local 422 if (deadline > now) { in dhcpv4_get_timeleft() 423 ret = (uint32_t)DIV_ROUND_UP(deadline - now, MSEC_PER_SEC); in dhcpv4_get_timeleft()
|
/Zephyr-latest/boards/ |
D | Kconfig | 88 the virtual time will jump to the next timer deadline instantly
|
/Zephyr-latest/include/zephyr/ |
D | kernel.h | 946 __syscall void k_thread_deadline_set(k_tid_t thread, int deadline);
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.12.rst | 50 * kernel: Earliest-deadline-first scheduling policy
|
D | release-notes-3.1.rst | 1515 * :github:`44671` - tests-ci : kernel: scheduler: deadline test failed 1735 * :github:`43276` - tests: up_squared: testsuite tests/kernel/sched/deadline/ failed
|
D | release-notes-2.6.rst | 1213 * :github:`35150` - [Coverity CID: 225136] Out-of-bounds write in tests/kernel/sched/deadline/src/m… 1991 * :github:`32000` - 2021 GSoC Call for Project Ideas - deadline Feb.19, 2021 12:00PM PST
|
D | release-notes-1.14.rst | 1693 * :github:`12541` - nrf timer handling exceeds bluetooth hard realtime deadline 2141 * :github:`9843` - tests/kernel/sched/deadline fails on NRF5x boards
|
D | release-notes-2.5.rst | 1114 * :github:`31508` - up_squared: tests/kernel/sched/deadline/ failed.
|
D | release-notes-2.7.rst | 1556 * :github:`36770` - doc:Missing description for deadline scheduling
|