CONFIG_XIP_KERNEL: Kernel Execute-In-Place from ROM

General informations

The Linux kernel configuration item CONFIG_XIP_KERNEL has multiple definitions:

Kernel Execute-In-Place from ROM found in arch/xtensa/Kconfig

The configuration item CONFIG_XIP_KERNEL:

• prompt: Kernel Execute-In-Place from ROM
• type: bool
• depends on: CONFIG_PLATFORM_HAVE_XIP
• defined in arch/xtensa/Kconfig
• found in Linux kernels: 5.5–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

Execute-In-Place allows the kernel to run from non-volatile storage directly addressable by the CPU, such as NOR flash. This saves RAM space since the text section of the kernel is not loaded from flash to RAM. Read-write sections, such as the data section and stack, are still copied to RAM. The XIP kernel is not compressed since it has to run directly from flash, so it will take more space to store it. The flash address used to link the kernel object files, and for storing it, is configuration dependent. Therefore, if you say Y here, you must know the proper physical address where to store the kernel image depending on your own flash memory usage.

Also note that the make target becomes "make xipImage" rather than "make Image" or "make uImage". The final kernel binary to put in ROM memory will be arch/xtensa/boot/xipImage.

If unsure, say N.

Kernel Execute-In-Place from ROM found in arch/riscv/Kconfig

The configuration item CONFIG_XIP_KERNEL:

• prompt: Kernel Execute-In-Place from ROM
• type: bool
• depends on: ( CONFIG_MMU && CONFIG_SPARSEMEM && CONFIG_NONPORTABLE ) && (! CONFIG_COMPILE_TEST )
• defined in arch/riscv/Kconfig
• found in Linux kernels: 5.13–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

Execute-In-Place allows the kernel to run from non-volatile storage directly addressable by the CPU, such as NOR flash. This saves RAM space since the text section of the kernel is not loaded from flash to RAM. Read-write sections, such as the data section and stack, are still copied to RAM. The XIP kernel is not compressed since it has to run directly from flash, so it will take more space to store it. The flash address used to link the kernel object files, and for storing it, is configuration dependent. Therefore, if you say Y here, you must know the proper physical address where to store the kernel image depending on your own flash memory usage.

Also note that the make target becomes "make xipImage" rather than "make zImage" or "make Image". The final kernel binary to put in ROM memory will be arch/riscv/boot/xipImage.

SPARSEMEM is required because the kernel text and rodata that are flash resident are not backed by memmap, then any attempt to get a struct page on those regions will trigger a fault.

If unsure, say N.

Kernel Execute-In-Place from ROM found in arch/arm/Kconfig

The configuration item CONFIG_XIP_KERNEL:

• prompt: Kernel Execute-In-Place from ROM
• type: bool
• depends on: (! CONFIG_ARM_LPAE && ! CONFIG_ARCH_MULTIPLATFORM ) && (! CONFIG_ARM_PATCH_IDIV && ! CONFIG_ARM_PATCH_PHYS_VIRT && ! CONFIG_SMP_ON_UP )
• defined in arch/arm/Kconfig
• found in Linux kernels: 2.6.10–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

Execute-In-Place allows the kernel to run from non-volatile storage directly addressable by the CPU, such as NOR flash. This saves RAM space since the text section of the kernel is not loaded from flash to RAM. Read-write sections, such as the data section and stack, are still copied to RAM. The XIP kernel is not compressed since it has to run directly from flash, so it will take more space to store it. The flash address used to link the kernel object files, and for storing it, is configuration dependent. Therefore, if you say Y here, you must know the proper physical address where to store the kernel image depending on your own flash memory usage.

Also note that the make target becomes "make xipImage" rather than "make zImage" or "make Image". The final kernel binary to put in ROM memory will be arch/arm/boot/xipImage.

If unsure, say N.

found in arch/blackfin/Kconfig

The configuration item CONFIG_XIP_KERNEL:

• prompt:
• type: bool
• depends on: CONFIG_ROMKERNEL
• defined in arch/blackfin/Kconfig
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.16

Help text

(none)

Execute In Place (XIP) kernel image found in arch/arm26/Kconfig

The configuration item CONFIG_XIP_KERNEL:

• prompt: Execute In Place (XIP) kernel image
• type: bool
• depends on: (none)
• defined in arch/arm26/Kconfig
• found in Linux kernels: 2.6.0–2.6.22

Help text

Select this option to create a kernel that can be programmed into the OS ROMs.

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: