Home
last modified time | relevance | path

Searched refs:stacks (Results 1 – 25 of 61) sorted by relevance

123

/linux-6.1.9/Documentation/x86/
Dkernel-stacks.rst7 Kernel stacks on x86-64 bit
15 active thread. These thread stacks are THREAD_SIZE (2*PAGE_SIZE) big.
16 These stacks contain useful data as long as a thread is alive or a
20 In addition to the per thread stacks, there are specialized stacks
21 associated with each CPU. These stacks are only used while the kernel
23 specialized stacks contain no useful data. The main CPU stacks are:
30 the split thread and interrupt stacks on i386, this gives more room
38 hardware stacks cannot nest without races.
46 point to dedicated stacks; each stack can be a different size.
58 Events with different IST codes (i.e. with different stacks) can be
[all …]
Dindex.rst16 kernel-stacks
/linux-6.1.9/Documentation/mm/
Dvmalloced-kernel-stacks.rst25 Virtually-mapped kernel stacks with guard pages causes kernel stack
30 support for virtually mapped stacks with guard pages. This feature
45 - vmalloc space must be large enough to hold many kernel stacks. This
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.
[all …]
Dindex.rst66 vmalloced-kernel-stacks
/linux-6.1.9/arch/arm64/kvm/hyp/nvhe/
Dstacktrace.c123 struct stack_info stacks[] = { in pkvm_save_backtrace() local
128 .stacks = stacks, in pkvm_save_backtrace()
129 .nr_stacks = ARRAY_SIZE(stacks), in pkvm_save_backtrace()
/linux-6.1.9/arch/arm64/kvm/
Dstacktrace.c181 struct stack_info stacks[] = { in hyp_dump_backtrace() local
186 .stacks = stacks, in hyp_dump_backtrace()
187 .nr_stacks = ARRAY_SIZE(stacks), in hyp_dump_backtrace()
/linux-6.1.9/arch/arm64/kernel/
Dstacktrace.c202 struct stack_info stacks[] = { in arch_stack_walk() local
217 .stacks = stacks, in arch_stack_walk()
218 .nr_stacks = ARRAY_SIZE(stacks), in arch_stack_walk()
/linux-6.1.9/samples/fprobe/
Dfprobe_example.c44 unsigned long stacks[BACKTRACE_DEPTH]; in show_backtrace() local
47 len = stack_trace_save(stacks, BACKTRACE_DEPTH, 2); in show_backtrace()
48 stack_trace_print(stacks, len, 24); in show_backtrace()
/linux-6.1.9/arch/sh/
DKconfig.debug26 bool "Use 4Kb for kernel stacks instead of 8Kb"
33 will also use IRQ stacks to compensate for the reduced stackspace.
36 bool "Use separate kernel stacks when processing interrupts"
39 If you say Y here the kernel will use separate kernel stacks
41 overflowing the process kernel stacks.
/linux-6.1.9/drivers/gpu/drm/i915/
Dintel_runtime_pm.c77 depot_stack_handle_t stack, *stacks; in track_intel_runtime_pm_wakeref() local
92 stacks = krealloc(rpm->debug.owners, in track_intel_runtime_pm_wakeref()
93 (rpm->debug.count + 1) * sizeof(*stacks), in track_intel_runtime_pm_wakeref()
95 if (stacks) { in track_intel_runtime_pm_wakeref()
96 stacks[rpm->debug.count++] = stack; in track_intel_runtime_pm_wakeref()
97 rpm->debug.owners = stacks; in track_intel_runtime_pm_wakeref()
/linux-6.1.9/arch/arm64/include/asm/stacktrace/
Dcommon.h45 struct stack_info *stacks; member
85 struct stack_info *info = &state->stacks[i]; in unwind_find_next_stack()
/linux-6.1.9/tools/perf/util/
Dbpf_lock_contention.c39 bpf_map__set_value_size(skel->maps.stacks, con->max_stack * sizeof(u64)); in lock_contention_prepare()
40 bpf_map__set_max_entries(skel->maps.stacks, con->map_nr_entries); in lock_contention_prepare()
119 stack = bpf_map__fd(skel->maps.stacks); in lock_contention_read()
/linux-6.1.9/Documentation/ia64/
Dmca.rst48 have to use their own, per-cpu stacks. The MCA/INIT stacks are
72 rendezvous interrupt are still running on their normal kernel stacks!
90 struct task and the kernel stacks. Then the MCA/INIT data would be
91 chained stacks like i386 interrupt stacks. But that required
95 stacks meant separate "tasks" for the MCA/INIT handlers.
136 stacks. ia64 has the struct task embedded in the single kernel
161 stacks are, which makes it too risky to copy the saved state to a user
/linux-6.1.9/tools/perf/util/bpf_skel/
Dlock_contention.bpf.c39 } stacks SEC(".maps");
121 pelem->stack_id = bpf_get_stackid(ctx, &stacks, BPF_F_FAST_STACK_CMP | stack_skip); in contention_begin()
Doff_cpu.bpf.c40 } stacks SEC(".maps");
197 stack_id = bpf_get_stackid(ctx, &stacks, in off_cpu_stat()
/linux-6.1.9/arch/arc/
DKconfig.debug4 bool "Use 16Kb for kernel stacks instead of 8Kb"
/linux-6.1.9/security/yama/
DKconfig10 Like capabilities, this security module stacks with other LSMs.
/linux-6.1.9/Documentation/translations/zh_CN/mm/
Dindex.rst59 vmalloced-kernel-stacks
Dvmalloced-kernel-stacks.rst4 :Original: Documentation/mm/vmalloced-kernel-stacks.rst
/linux-6.1.9/Documentation/dev-tools/
Dkmemleak.rst47 enable the task stacks scanning (default)
49 disable the tasks stacks scanning
101 2. scan the memory starting with the data section and stacks, checking
186 kmemleak_erase functions (see above). The task stacks also increase the
197 stacks. Kmemleak defines MSECS_MIN_AGE (defaulting to 1000) representing
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-devices-mapping9 For example, on 4-die Xeon platform with up to 6 IIO stacks per
/linux-6.1.9/arch/parisc/
DKconfig294 bool "Use separate kernel stacks when processing interrupts"
297 If you say Y here the kernel will use separate kernel stacks
299 overflowing the process kernel stacks.
/linux-6.1.9/net/6lowpan/
DKconfig7 "6LoWPAN" which is supported by IEEE 802.15.4 or Bluetooth stacks.
/linux-6.1.9/Documentation/x86/x86_64/
Dmm.rst61 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks
120 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks
/linux-6.1.9/arch/arm/lib/
Dbacktrace.S103 @ Kernel stacks may be discontiguous in memory. If the next

123