The latest development version of this page may be more current than this released 2.7.0 version.

CONFIG_SCHED_IPI_SUPPORTED¶

(No prompt – not directly user assignable.)

Type: bool

Help¶

True if the architecture supports a call to
arch_sched_ipi() to broadcast an interrupt that will call
z_sched_ipi() on other CPUs in the system.  Required for
k_thread_abort() to operate with reasonable latency
(otherwise we might have to wait for the other thread to
take an interrupt, which can be arbitrarily far in the
future).

Defaults¶

Symbols that select this symbol¶

Kconfig definitions¶

At soc/xtensa/intel_adsp/cavs_v15/Kconfig.defconfig.series:77

Included via Kconfig:8 → Kconfig.zephyr:27 → soc/xtensa/intel_adsp/Kconfig.defconfig:6

Menu path: (Top)

config SCHED_IPI_SUPPORTED
    bool
    default y if IPM_CAVS_IDC
    depends on SMP && SOC_SERIES_INTEL_CAVS_V15

At soc/xtensa/intel_adsp/cavs_v18/Kconfig.defconfig.series:81

Included via Kconfig:8 → Kconfig.zephyr:27 → soc/xtensa/intel_adsp/Kconfig.defconfig:6

Menu path: (Top)

config SCHED_IPI_SUPPORTED
    bool
    default y if IPM_CAVS_IDC
    depends on SMP && SOC_SERIES_INTEL_CAVS_V18

At soc/xtensa/intel_adsp/cavs_v20/Kconfig.defconfig.series:81

Included via Kconfig:8 → Kconfig.zephyr:27 → soc/xtensa/intel_adsp/Kconfig.defconfig:6

Menu path: (Top)

config SCHED_IPI_SUPPORTED
    bool
    default y if IPM_CAVS_IDC
    depends on SMP && SOC_SERIES_INTEL_CAVS_V20

At soc/xtensa/intel_s1000/Kconfig.defconfig:51

Included via Kconfig:8 → Kconfig.zephyr:27

Menu path: (Top)

config SCHED_IPI_SUPPORTED
    bool
    default y if IPM_CAVS_IDC
    depends on SMP && SOC_INTEL_S1000

At kernel/Kconfig:817

Included via Kconfig:8 → Kconfig.zephyr:40

Menu path: (Top) → General Kernel Options → SMP Options

config SCHED_IPI_SUPPORTED
    bool
    help
      True if the architecture supports a call to
      arch_sched_ipi() to broadcast an interrupt that will call
      z_sched_ipi() on other CPUs in the system.  Required for
      k_thread_abort() to operate with reasonable latency
      (otherwise we might have to wait for the other thread to
      take an interrupt, which can be arbitrarily far in the
      future).

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