:orphan:

.. title:: ARCH_MEM_DOMAIN_DATA

.. option:: CONFIG_ARCH_MEM_DOMAIN_DATA

*(No prompt -- not directly user assignable.)*

Type: ``bool``

Help
====

.. code-block:: none

    This hidden option is selected by the target architecture if
    architecture-specific data is needed on a per memory domain basis.
    If so, the architecture defines a 'struct arch_mem_domain' which is
    embedded within every struct k_mem_domain. The architecture
    must also define the arch_mem_domain_init() function to set this up
    when a memory domain is created.

    Typical uses might be a set of page tables for that memory domain.

Direct dependencies
===================

\ :option:`USERSPACE <CONFIG_USERSPACE>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols that select this symbol
===============================

- \ :option:`ARM_MMU <CONFIG_ARM_MMU>`
- \ :option:`X86 <CONFIG_X86>`

Kconfig definition
==================



At ``<Zephyr Kernel>/Kconfig:725``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:30``

Menu path: (Top) → General Kernel Options

.. code-block:: kconfig

    config ARCH_MEM_DOMAIN_DATA
    	bool
    	depends on USERSPACE
    	help
    	  This hidden option is selected by the target architecture if
    	  architecture-specific data is needed on a per memory domain basis.
    	  If so, the architecture defines a 'struct arch_mem_domain' which is
    	  embedded within every struct k_mem_domain. The architecture
    	  must also define the arch_mem_domain_init() function to set this up
    	  when a memory domain is created.
	  
    	  Typical uses might be a set of page tables for that memory domain.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*