Lines Matching refs:stack
240 the API needed to access registers and stack entries from pt_regs,
287 Support user stack dumps for perf event samples. This needs
288 access to the user stack pointer which is not unified across
364 - it has implemented a stack canary (e.g. __stack_chk_guard)
369 Set when a stack-protector mode is enabled, so that the build
377 This option turns on the "stack-protector" GCC feature. This
379 the stack just before the return address, and validates
388 Disable "stack-protector" GCC feature.
394 Functions will have the stack-protector canary logic added if they
395 have an 8-byte or larger character array on the stack.
408 Functions will have the stack-protector canary logic added in any
495 Architecture doesn't only execute the irq handler on the irq stack
497 stack instead of switching to a new one when we call __do_softirq()
499 This spares a stack switch and improves cache usage on softirq
510 stack, mmap, brk, and ET_DYN. Defined functions: