CONFIG_ARM_PATCH_PHYS_VIRT: Patch physical to virtual translations at runtime

General informations

The Linux kernel configuration item CONFIG_ARM_PATCH_PHYS_VIRT has multiple definitions:

Patch physical to virtual translations at runtime found in arch/arm/Kconfig

The configuration item CONFIG_ARM_PATCH_PHYS_VIRT:

• prompt: Patch physical to virtual translations at runtime
• type: bool
• depends on: (! CONFIG_ARCH_MULTIPLATFORM ) && ( CONFIG_MMU )
• defined in arch/arm/Kconfig
• found in Linux kernels: 3.1–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

Patch phys-to-virt and virt-to-phys translation functions at boot and module load time according to the position of the kernel in system memory.

This can only be used with non-XIP MMU kernels where the base of physical memory is at a 2 MiB boundary.

Only disable this option if you know that you do not require this feature (eg, building a kernel for a single machine) and you need to shrink the kernel to the minimal size.

Patch physical to virtual translations at runtime (EXPERIMENTAL) found in arch/arm/Kconfig

The configuration item CONFIG_ARM_PATCH_PHYS_VIRT:

• prompt: Patch physical to virtual translations at runtime (EXPERIMENTAL)
• type: bool
• depends on: ( CONFIG_EXPERIMENTAL ) && (! CONFIG_XIP_KERNEL && CONFIG_MMU ) && (! CONFIG_ARCH_REALVIEW || ! CONFIG_SPARSEMEM )
• defined in arch/arm/Kconfig
• found in Linux kernels: 2.6.39, 3.0

Help text

Patch phys-to-virt and virt-to-phys translation functions at boot and module load time according to the position of the kernel in system memory.

This can only be used with non-XIP MMU kernels where the base of physical memory is at a 16MB boundary, or theoretically 64K for the MSM machine class.

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: