CONFIG_DEBUG_PER_CPU_MAPS: Debug access to per_cpu maps

General informations

The Linux kernel configuration item CONFIG_DEBUG_PER_CPU_MAPS has multiple definitions:

Debug access to per_cpu maps found in lib/Kconfig.debug

The configuration item CONFIG_DEBUG_PER_CPU_MAPS:

• prompt: Debug access to per_cpu maps
• type: bool
• depends on: ( CONFIG_DEBUG_KERNEL ) && ( CONFIG_SMP )
• defined in lib/Kconfig.debug
• found in Linux kernels: 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.11, 6.12-rc+HEAD

Help text

Say Y to verify that the per_cpu map being accessed has been set up. This adds a fair amount of code to kernel memory and decreases performance.

Say N if unsure.

Debug access to per_cpu maps found in arch/x86/Kconfig.debug

The configuration item CONFIG_DEBUG_PER_CPU_MAPS:

• prompt: Debug access to per_cpu maps
• type: bool
• depends on: ( CONFIG_DEBUG_KERNEL ) && ( CONFIG_SMP )
• defined in arch/x86/Kconfig.debug
• found in Linux kernels: 2.6.25–2.6.39

Help text

Say Y to verify that the per_cpu map being accessed has been setup. Adds a fair amount of code to kernel memory and decreases performance.

Say N if unsure.

Debug access to per_cpu maps found in arch/powerpc/Kconfig.debug

The configuration item CONFIG_DEBUG_PER_CPU_MAPS:

• prompt: Debug access to per_cpu maps
• type: bool
• depends on: ( CONFIG_DEBUG_KERNEL ) && ( CONFIG_SMP )
• defined in arch/powerpc/Kconfig.debug
• found in Linux kernels: 2.6.35–2.6.39

Help text

Say Y to verify that the per_cpu map being accessed has been setup. Adds a fair amount of code to kernel memory and decreases performance.

Say N if unsure.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: