spec: Move application configuration items

1 files changed, 43 insertions, 0 deletions

diff --git a/spec/if/acfg/interrupt-stack-size.yml b/spec/if/acfg/interrupt-stack-size.yml
new file mode 100644
index 00000000..b2986237
--- /dev/null
+++ b/spec/if/acfg/interrupt-stack-size.yml
@@ -0,0 +1,43 @@
+SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
+appl-config-option-type: integer
+constraints: {}
+copyrights:
+- Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
+default-value: |
+  The default value is :ref:`BSP_INTERRUPT_STACK_SIZE` in case it is defined,
+  otherwise the default value is ``CPU_STACK_MINIMUM_SIZE``.
+description: |
+  The value of this configuration option defines the size of an interrupt stack
+  in bytes.
+enabled-by: true
+index-entries:
+- interrupt stack size
+interface-type: appl-config-option
+links:
+- role: appl-config-group-member
+  uid: group-general
+- role: constraint
+  uid: constraint-isrstackalign
+- role: constraint
+  uid: constraint-isrstackarea
+- role: constraint
+  uid: constraint-bspappmin
+name: CONFIGURE_INTERRUPT_STACK_SIZE
+notes: |
+  There is one interrupt stack available for each configured processor
+  (:ref:`CONFIGURE_MAXIMUM_PROCESSORS`).  The interrupt stack areas are
+  statically allocated in a special linker section (``.rtemsstack.interrupt``).
+  The placement of this linker section is BSP-specific.
+
+  Some BSPs use the interrupt stack as the initialization stack which is used
+  to perform the sequential system initialization before the multithreading
+  is started.
+
+  The interrupt stacks are covered by the :ref:`stack checker
+  <CONFIGURE_STACK_CHECKER_ENABLED>`.  However, using a too small interrupt
+  stack size may still result in undefined behaviour.
+
+  In releases before RTEMS 5.1 the default value was
+  :ref:`CONFIGURE_MINIMUM_TASK_STACK_SIZE` instead of ``CPU_STACK_MINIMUM_SIZE``.
+text: ''
+type: interface