Lines Matching full:stacks

15 series that introduced the `Virtually Mapped Kernel Stacks feature
25 Virtually mapped kernel stacks with guard pages cause kernel stack
30 support for virtually mapped stacks with guard pages. This feature
42 Architectures that can support Virtually Mapped Kernel Stacks should
45 - vmalloc space must be large enough to hold many kernel stacks. This
47 - Stacks in vmalloc space need to work reliably.  For example, if
61 mapped task stacks. This option depends on HAVE_ARCH_VMAP_STACK.
63 - Enable this if you want the use virtually-mapped kernel stacks
94 - Allocated stacks are cached and later reused by new threads, so memcg
95   accounting is performed manually on assigning/releasing stacks to tasks.
100 - On arm64, all VMAP's stacks need to have the same alignment to ensure
103 - This does not address interrupt stacks - according to the original patch
114 virtually mapped kernel stacks are enabled.
146 - A percpu cache of vmalloced stacks appears to be a bit faster than a
152   waiting for RCU) and then, if vmapped stacks are in use, cache the