| /Zephyr-Core-3.4.0/tests/drivers/counter/maxim_ds3231_api/src/ |
| D | test_counter.c | 527 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_instance() local
535 err = counter_set_guard_period(dev, guard, in test_late_alarm_instance()
577 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_error_instance() local
584 err = counter_set_guard_period(dev, guard, in test_late_alarm_error_instance()
611 uint32_t guard = counter_get_guard_period(dev, in late_detection_capable() local
613 int err = counter_set_guard_period(dev, guard, in late_detection_capable()
|
| /Zephyr-Core-3.4.0/arch/arc/core/mpu/ |
| D | Kconfig | 25 If your core supports that, it is preferred over MPU stack guard.
|
| /Zephyr-Core-3.4.0/tests/drivers/counter/counter_basic_api/src/ |
| D | test_counter.c | 650 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_instance() local
658 err = counter_set_guard_period(dev, guard, in test_late_alarm_instance()
702 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_error_instance() local
709 err = counter_set_guard_period(dev, guard, in test_late_alarm_error_instance()
736 uint32_t guard = counter_get_guard_period(dev, in late_detection_capable() local
738 int err = counter_set_guard_period(dev, guard, in late_detection_capable()
|
| /Zephyr-Core-3.4.0/doc/kernel/usermode/ |
| D | mpu_userspace.rst | 19 guard (if applicable).
|
| D | mpu_stack_objects.rst | 31 occur, a fault ensues. The stack guard is defined at the bottom (the lowest
|
| D | memory_domain.rst | 62 Some systems implement this feature by creating at runtime a 'guard' MPU region
|
| /Zephyr-Core-3.4.0/drivers/counter/ |
| D | counter_nrfx_timer.c | 306 static int set_guard_period(const struct device *dev, uint32_t guard, in set_guard_period() argument
311 __ASSERT_NO_MSG(guard < get_top_value(dev)); in set_guard_period()
313 data->guard_period = guard; in set_guard_period()
|
| D | counter_gd32_timer.c | 372 uint32_t guard, uint32_t flags) in counter_gd32_timer_set_guard_period() argument
376 __ASSERT_NO_MSG(guard < counter_gd32_timer_get_top_value(dev)); in counter_gd32_timer_set_guard_period()
378 data->guard_period = guard; in counter_gd32_timer_set_guard_period()
|
| D | counter_ll_stm32_timer.c | 525 static int counter_stm32_set_guard_period(const struct device *dev, uint32_t guard, in counter_stm32_set_guard_period() argument
531 __ASSERT_NO_MSG(guard < counter_stm32_get_top_value(dev)); in counter_stm32_set_guard_period()
533 data->guard_period = guard; in counter_stm32_set_guard_period()
|
| D | counter_nrfx_rtc.c | 574 static int set_guard_period(const struct device *dev, uint32_t guard, in set_guard_period() argument
579 data->guard_period = guard; in set_guard_period()
|
| /Zephyr-Core-3.4.0/subsys/ipc/ipc_service/lib/ |
| D | Kconfig.icmsg | 27 multiple contexts. Mutex is used to guard access to the memory.
|
| /Zephyr-Core-3.4.0/arch/arm/core/aarch32/mpu/ |
| D | Kconfig | 30 guard, user thread stack, and application memory domains), if the
74 Floating Point (FP) context. The width of the guard is set to
|
| /Zephyr-Core-3.4.0/doc/hardware/porting/ |
| D | arch.rst | 576 * For systems that implement stack protection using a guard memory region,
577 it's possible to overshoot the guard and corrupt adjacent data structures
585 CPU features for this purpose, or special read-only guard regions immediately
615 on write. Reserved memory will be used for the guard region.
622 MMU-based systems should not reserve RAM for the guard region and instead
641 the guard is unnecessary and shouldn't be unconditionally reserved.
645 * The required guard size is variable and depends on context. For example, some
648 completely overshooting a minimally-sized guard and corrupting adjacent
649 memory. Rather than unconditionally reserving a larger guard, the extra
660 system calls. If stack guards are implemented, a stack guard region must
[all …]
|
| /Zephyr-Core-3.4.0/arch/arm/core/aarch32/ |
| D | Kconfig | 192 - the MPU-based stack guard
195 The two stack guard options are mutually exclusive. The
197 prioritized over the MPU-based stack guard. The developer
199 stack guard, if this is desired.
|
| /Zephyr-Core-3.4.0/arch/x86/core/ |
| D | Kconfig.intel64 | 79 by preceding all stack areas with a 4K guard page.
|
| D | Kconfig.ia32 | 73 by preceding all stack areas with a 4K guard page.
|
| /Zephyr-Core-3.4.0/arch/arm64/core/cortex_r/ |
| D | Kconfig | 27 guard, user thread stack, and application memory domains), if the
|
| /Zephyr-Core-3.4.0/arch/riscv/ |
| D | Kconfig | 255 The Hardware Stack Protection implements a guard area at the bottom
257 guard area not accessible.
259 This is the size of the guard area. This should be large enough to
|
| /Zephyr-Core-3.4.0/arch/arc/ |
| D | Kconfig | 240 - the MPU-based stack guard
243 The two stack guard options are mutually exclusive. The
245 prioritized over the MPU-based stack guard.
|
| /Zephyr-Core-3.4.0/cmake/compiler/arcmwdt/ |
| D | compiler_flags.cmake | 174 #no support of -mstack-protector-guard=global"
|
| /Zephyr-Core-3.4.0/cmake/compiler/gcc/ |
| D | compiler_flags.cmake | 163 check_set_compiler_property(APPEND PROPERTY security_canaries -mstack-protector-guard=global)
|
| /Zephyr-Core-3.4.0/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 161 memories, and/or programs a stack-overflow MPU guard at the bottom of the thread's
415 the stack guard (in certain Arm v8-M configurations with :kconfig:option:`CONFIG_MPU_GAP_FILLING`
416 enabled 2 MPU regions are required to implement the guard feature)
504 * a read-only region for the MPU stack guard
|
| /Zephyr-Core-3.4.0/doc/kernel/services/other/ |
| D | fatal.rst | 206 implemented via dedicated CPU features, or read-only MMU/MPU guard regions
|
| D | float.rst | 99 the thread's guard region to always guarantee stack overflow detection,
|
| /Zephyr-Core-3.4.0/doc/kernel/services/threads/ |
| D | index.rst | 178 - If guard-based stack overflow detection is enabled, a small write-
|
