:orphan:

.. title:: DEMAND_PAGING_ALLOW_IRQ

.. option:: CONFIG_DEMAND_PAGING_ALLOW_IRQ

*Allow interrupts during page-ins/outs*

Type: ``bool``

Help
====

Allow interrupts to be serviced while pages are being evicted or
retrieved from the backing store. This is much better for system
latency, but any code running in interrupt context that page faults
will cause a kernel panic. Such code must work with exclusively pinned
code and data pages.

The scheduler is still disabled during this operation.

If this option is disabled, the page fault servicing logic
runs with interrupts disabled for the entire operation. However,
ISRs may also page fault.

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

\ :option:`DEMAND_PAGING <CONFIG_DEMAND_PAGING>` && \ :option:`MMU <CONFIG_MMU>`

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

Defaults
========

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

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

.. highlight:: kconfig

At ``arch/Kconfig:646``

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

Menu path: (Top) → Enable MMU features → Enable demand paging [EXPERIMENTAL]

.. parsed-literal::

    config DEMAND_PAGING_ALLOW_IRQ
    	bool "Allow interrupts during page-ins/outs"
    	depends on \ :option:`DEMAND_PAGING <CONFIG_DEMAND_PAGING>` && \ :option:`MMU <CONFIG_MMU>`
    	help
    	  Allow interrupts to be serviced while pages are being evicted or
    	  retrieved from the backing store. This is much better for system
    	  latency, but any code running in interrupt context that page faults
    	  will cause a kernel panic. Such code must work with exclusively pinned
    	  code and data pages.
	  
    	  The scheduler is still disabled during this operation.
	  
    	  If this option is disabled, the page fault servicing logic
    	  runs with interrupts disabled for the entire operation. However,
    	  ISRs may also page fault.

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