/Zephyr-latest/drivers/pwm/ |
D | pwm_mcux_ftm.c | 59 uint32_t overflows; member 295 capture->first_edge_overflows = data->overflows; in mcux_ftm_capture_first_edge() 307 uint32_t second_edge_overflows = data->overflows; in mcux_ftm_capture_second_edge() 310 uint32_t overflows; in mcux_ftm_capture_second_edge() local 340 overflows = second_edge_overflows - capture->first_edge_overflows; in mcux_ftm_capture_second_edge() 343 if (overflows > 0) { in mcux_ftm_capture_second_edge() 344 if (u32_mul_overflow(overflows, config->base->MOD, &cycles)) { in mcux_ftm_capture_second_edge() 361 pair, capture->first_edge_overflows, second_edge_overflows, overflows, first_cnv, in mcux_ftm_capture_second_edge() 392 data->overflows++; in mcux_ftm_handle_overflow()
|
D | pwm_renesas_ra.c | 34 uint32_t overflows; member 414 (data->capture.overflows * period) + p_args->capture; in fsp_callback() 420 (data->capture.overflows * period) + p_args->capture; in fsp_callback() 424 data->capture.overflows = 0U; in fsp_callback() 431 data->capture.overflows++; in fsp_callback()
|
D | pwm_stm32.c | 58 uint32_t overflows; member 607 data->capture.overflows = 0u; in pwm_stm32_enable_capture() 684 cpt->overflows++; in pwm_stm32_isr() 734 if (cpt->overflows) { in pwm_stm32_isr() 741 cpt->overflows = 0u; in pwm_stm32_isr()
|
D | pwm_mcux_pwt.c | 194 static int mcux_pwt_calc_pulse(uint16_t pw, uint32_t overflows, in mcux_pwt_calc_pulse() argument 200 if (u32_mul_overflow(overflows, 0xFFFFU, &pulse)) { in mcux_pwt_calc_pulse()
|
D | pwm_numaker.c | 60 uint32_t overflows; member
|
/Zephyr-latest/include/zephyr/linker/ |
D | kobject-text.ld | 28 when the area overflows we need to temporarily corrupt the
|
/Zephyr-latest/doc/kernel/services/other/ |
D | fatal.rst | 195 If a thread is running in user mode, then stack overflows are always caught, 202 not enabled, depending on configuration stack overflows may or may not be 204 architectures and will catch stack overflows in supervisor mode, including 207 placed immediately adjacent to the stack buffer. Stack overflows caught in this
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_timeout.rst | 22 number (``INT32_MAX``), which overflows at 24 days 20 hours 31 minutes 23.648
|
/Zephyr-latest/doc/kernel/usermode/ |
D | memory_domain.rst | 51 buffer overflows when the system is running in supervisor mode. This 59 know when these overflows happen, as without robust detection logic the system 61 stack buffer overflows. 65 preceding the supervisor mode stack buffer. If the stack overflows an 68 This feature is optional and is not required to catch stack overflows in user 71 Other systems may have dedicated CPU support for catching stack overflows
|
D | overview.rst | 82 - We ensure the detection and safe handling of user mode stack overflows. 126 - Stack overflows for threads running in supervisor mode may be caught,
|
/Zephyr-latest/doc/hardware/porting/ |
D | arch.rst | 578 in supervisor mode overflows its stack. This is useful for debugging, although 597 :kconfig:option:`CONFIG_HW_STACK_PROTECTION` only catches stack overflows for 601 This feature only detects supervisor mode stack overflows, including stack 602 overflows when handling system calls. It doesn't guarantee that the kernel has 607 Stack overflows in user mode are recoverable (from the kernel's perspective) 609 only applies to catching overflows when the CPU is in supervisor mode. 614 If we are detecting stack overflows in supervisor mode via special CPU 622 We are detecting supervisor mode stack overflows via special memory protection 724 stack overflows.
|
D | board_porting.rst | 672 kernel to detect stack overflows when the system is running in privileged
|
/Zephyr-latest/doc/hardware/arch/ |
D | arm_cortex_m.rst | 193 Stack overflows trigger the dedicated UsageFault exception provided by Arm v8-M. 408 * stack overflows are triggering processor faults as soon as they occur 409 * the mechanism is essential for detecting stack overflows in supervisor threads, or 410 user threads in privileged mode; stack overflows in threads in user mode will always be 412 * stack overflows are always detected, however, the mechanism does not guarantee that
|
/Zephyr-latest/doc/security/ |
D | secure-coding.rst | 211 mitigate linear stack/heap buffer overflows, non-linear out of bound writes, 212 integer overflows, and other integer issues. The follow-on class, `OST2_1002`_,
|
/Zephyr-latest/cmake/compiler/gcc/ |
D | compiler_flags.cmake | 190 # _FORTIFY_SOURCE: Detect common-case buffer overflows for certain functions
|
/Zephyr-latest/arch/arm64/core/ |
D | Kconfig | 142 overflows during the exception happens from EL1. This stack is not
|
/Zephyr-latest/arch/ |
D | Kconfig | 289 catch stack overflows when the system is running in privileged 310 If a user thread overflows its stack, this will be caught and the 312 may or may not catch stack overflows when the system is in
|
/Zephyr-latest/arch/riscv/ |
D | Kconfig | 370 of the stack using the PMP to catch stack overflows by marking that
|
/Zephyr-latest/subsys/debug/ |
D | Kconfig | 213 with stack overflows, knowledge that this is happening is very
|
/Zephyr-latest/ |
D | Kconfig.zephyr | 538 default stack sizes in order to avoid stack overflows. 575 prompt "Detect buffer overflows in libc calls"
|
D | CMakeLists.txt | 163 # Kconfig.zephyr "Detect buffer overflows in libc calls" is a kconfig choice, 175 # @Intent: Set compiler flags to detect general stack overflows across all functions
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.14.rst | 640 overflows or induced in user mode 1147 * :github:`15206` - sanitycheck --coverage: stack overflows on qemu_x86, mps2_an385 and qemu_x86_no… 1307 * :github:`14500` - sanitycheck --coverage: stack overflows on qemu_x86 and mps2_an385 1308 * :github:`14499` - sanitycheck --coverage on qemu_x86: stack overflows on qemu_x86 and mps2_an385 1566 * :github:`13342` - arm: user thread stack overflows do not report _NANO_ERR_STACK_CHK_FAIL 1567 * :github:`13341` - arc: user thread stack overflows do not report _NANO_ERR_STACK_CHK_FAIL 2221 * :github:`7706` - ARM NXP hardware stack overflows do not report _NANO_ERR_STACK_CHK_FAIL or provi…
|
/Zephyr-latest/boards/native/doc/ |
D | bsim_boards_design.rst | 371 issues related to access to structures members or array overflows.
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 715 overflows, integer overflows, uninitialized variables, and many more.
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | index.rst | 180 to catch overflows.
|