Help¶

There’s a spinlock validation framework available when asserts are enabled. It adds a relatively hefty overhead (about 3k or so) to kernel code size, don’t use on platforms known to be small.

Direct dependencies¶

ASSERT && MP_NUM_CPUS < 4

(Includes any dependencies from ifs and menus.)

Default¶

y if !FLASH || FLASH_SIZE > 32

Kconfig definition¶

At <Zephyr>/subsys/debug/Kconfig:222

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:17

Menu path: (Top) → Sub Systems and OS Services → Debugging Options → Enable __ASSERT() macro

config SPIN_VALIDATE
    bool "Enable spinlock validation"
    default y if !FLASH || FLASH_SIZE > 32
    depends on ASSERT && MP_NUM_CPUS < 4
    help
      There's a spinlock validation framework available when asserts are
      enabled. It adds a relatively hefty overhead (about 3k or so) to
      kernel code size, don't use on platforms known to be small.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)