Home
last modified time | relevance | path

Searched refs:kernel (Results 1 – 25 of 216) sorted by relevance

123456789

/tools/testing/selftests/ftrace/test.d/ftrace/
Dfunc_stack_tracer.tc9 echo 1 > /proc/sys/kernel/stack_tracer_enabled
19 echo 0 > /proc/sys/kernel/stack_tracer_enabled
25 echo 1 > /proc/sys/kernel/stack_tracer_enabled
35 echo 0 > /proc/sys/kernel/stack_tracer_enabled
Dfgraph-filter-stack.tc10 if [ -e /proc/sys/kernel/stack_tracer_enabled ]; then
11 echo 0 > /proc/sys/kernel/stack_tracer_enabled
36 echo 1 > /proc/sys/kernel/stack_tracer_enabled
55 echo 0 > /proc/sys/kernel/stack_tracer_enabled
/tools/testing/selftests/livepatch/
Dfunctions.sh56 DYNAMIC_DEBUG=$(grep '^kernel/livepatch' /sys/kernel/debug/dynamic_debug/control | \
58 FTRACE_ENABLED=$(sysctl --values kernel.ftrace_enabled)
63 echo -n "$DYNAMIC_DEBUG" > /sys/kernel/debug/dynamic_debug/control
66 sysctl kernel.ftrace_enabled="$FTRACE_ENABLED" &> /dev/null
71 cat <<-EOF > /sys/kernel/debug/dynamic_debug/control
72 file kernel/livepatch/* +p
78 result=$(sysctl -q kernel.ftrace_enabled="$1" 2>&1 && \
79 sysctl kernel.ftrace_enabled 2>&1)
240 echo 0 > /sys/kernel/livepatch/"$mod"/enabled
DREADME5 This is a small set of sanity tests for the kernel livepatching.
7 The test suite loads and unloads several test kernel modules to verify
8 livepatch behavior. Debug information is logged to the kernel's message
25 Test kernel modules are built as part of lib/ (make modules) and need to
29 To run the livepatch selftests, from the top of the kernel source tree:
39 check_result(). The latter function greps the kernel's ring buffer for
/tools/memory-model/Documentation/
DREADME4 Linux-kernel memory model (LKMM) audience might be anywhere from novice
5 to expert both in kernel hacking and in understanding LKMM.
12 o You are new to Linux-kernel concurrency: simple.txt
14 o You have some background in Linux-kernel concurrency, and would
16 that the Linux kernel provides: ordering.txt
20 o You are familiar with the Linux-kernel concurrency primitives
24 o You are familiar with Linux-kernel concurrency, and would
31 o You are familiar with Linux-kernel concurrency and the use of
34 o You are familiar with Linux-kernel concurrency and the use
51 Quick-reference guide to the Linux-kernel memory model.
[all …]
/tools/lib/traceevent/Documentation/
Dlibtraceevent-header_page.txt7 Get the data stored in the header page, in kernel context.
21 These functions retrieve information from kernel context, stored in tracefs
26 in kernel context. The _tep_ argument is trace event parser context.
30 in kernel context. The _tep_ argument is trace event parser context. This
33 The _tep_is_old_format()_ function returns true if the kernel predates
44 The _tep_is_old_format()_ function returns true, if an old kernel is used to
45 generate the tracing data, which has no event/header_page. If the kernel is new,
64 printf ("%s kernel is used to generate the tracing data.\n",
94 Report bugs to <linux-trace-devel@vger.kernel.org>
102 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Dlibtraceevent-func_apis.txt27 Some tools may have already a way to resolve the kernel functions. These APIs
30 The _tep_func_resolver_t_ type is the prototype of the alternative kernel
32 (set with the _tep_set_function_resolver()_ call ) and the address of a kernel
37 kernel functions resolver. The _tep_ argument is trace event parser context.
43 The _tep_reset_function_resolver()_ function resets the kernel functions
66 start address of the function. The _mod_ is the kernel module the function may
70 it was stored in the kernel. Some strings internal to the kernel with static
73 tep_register_print_string() supplies the parsing with the mapping between kernel
175 Report bugs to <linux-trace-devel@vger.kernel.org>
183 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Dlibtraceevent-parse_head.txt44 buf = read_file("/sys/kernel/tracing/events/header_page", &size);
74 Report bugs to <linux-trace-devel@vger.kernel.org>
82 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
/tools/lib/traceevent/
Dlibtraceevent.pc.template6 URL: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
7 Description: Linux kernel trace event library
/tools/testing/selftests/fpu/
Drun_test_fpu.sh30 if [ ! -e /sys/kernel/debug/selftest_helpers/test_fpu ]; then
31 mount -t debugfs none /sys/kernel/debug
33 if [ ! -e /sys/kernel/debug/selftest_helpers/test_fpu ]; then
/tools/memory-model/
Dlinux-kernel.cfg1 macros linux-kernel.def
2 bell linux-kernel.bell
3 model linux-kernel.cat
DREADME10 short) of the Linux kernel, written in the "cat" language and executable
15 to convert a litmus test to a Linux kernel module, which in turn allows
16 that litmus test to be exercised within the Linux kernel.
35 a later release of Linux kernel.
41 dependency on a target kernel release where converted code is built
42 and executed. Any change in kernel APIs essential to klitmus7 will
70 Example litmus tests may be found in the Linux-kernel source tree:
78 https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git/tree/CodeSamples/formal/herd
79 https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git/tree/CodeSamples/formal/litmus
92 $ herd7 -conf linux-kernel.cfg litmus-tests/SB+fencembonceonces.litmus
[all …]
/tools/testing/selftests/powerpc/security/
Dmitigation-patching.sh31 cd /sys/kernel/debug/powerpc || rc=1
37 tainted=$(cat /proc/sys/kernel/tainted)
68 tainted=$(cat /proc/sys/kernel/tainted)
/tools/bpf/bpftool/Documentation/
Dbpftool-feature.rst5 tool for inspection of eBPF-related parameters for Linux kernel or net device
25 | *COMPONENT* := { **kernel** | **dev** *NAME* }
29 **bpftool feature probe** [**kernel**] [**full**] [**macros** [**prefix** *PREFIX*]]
30 Probe the running kernel and dump a number of eBPF-related
37 helpers which print warnings to kernel logs. To enable them
49 Keyword **kernel** can be omitted. If no probe target is
50 specified, probing the kernel is the default behaviour.
67 same role as when probing the kernel.
Dbpftool-iter.rst31 A bpf iterator combines a kernel iterating of
32 particular kernel data (e.g., tasks, bpf_maps, etc.)
33 and a bpf program called for each kernel data object
35 *read* kernel iterator output through *read()* syscall.
45 that map. User can have a bpf program in kernel to run
/tools/testing/selftests/vm/
Drun_vmtests.sh83 shmmax=`cat /proc/sys/kernel/shmmax`
84 shmall=`cat /proc/sys/kernel/shmall`
85 echo 268435456 > /proc/sys/kernel/shmmax
86 echo 4194304 > /proc/sys/kernel/shmall
97 echo $shmmax > /proc/sys/kernel/shmmax
98 echo $shmall > /proc/sys/kernel/shmall
/tools/debugging/
DMakefile8 TARGET = kernel-chktaint
14 install: kernel-chktaint
/tools/testing/selftests/pstore/
Dpstore_crash_test16 echo 1 > /proc/sys/kernel/sysrq
18 echo 3 > /proc/sys/kernel/panic
/tools/perf/Documentation/
Dperf-buildid-list.txt19 It can also be used to show the build id of the running kernel or in an ELF
34 --kernel::
35 Show running kernel build id.
Dperf-kallsyms.txt6 perf-kallsyms - Searches running kernel for symbols
15 This command searches the running kernel kallsyms file for the given symbol(s)
Dsecurity.txt6 https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html
51 + kernel
112 8. Reboot machine and it will label filesystems and load Targeted policy into the kernel;
132 processes. MAC policy settings (e.g. SELinux) can be loaded into the kernel
142 Consider adjusting /proc/sys/kernel/perf_event_paranoid setting to open
150 >= 2: Disallow kernel profiling
152 in /etc/sysctl.conf (e.g. kernel.perf_event_paranoid = <setting>)
178 class perf_event { cpu kernel open read tracepoint write };
182 allow unconfined_t self:perf_event { cpu kernel open read tracepoint write };
184 Now compile, pack and load my-perf.pp extension module into the kernel:
[all …]
/tools/testing/vsock/
DREADME14 1. Build the kernel, make headers_install, and build these tests.
15 2. Install the kernel and tests on the host.
16 3. Install the kernel and tests inside the guest.
/tools/perf/
Dcheck-headers.sh156 check_2 tools/perf/arch/powerpc/entry/syscalls/syscall.tbl arch/powerpc/kernel/syscalls/syscall.tbl
157 check_2 tools/perf/arch/s390/entry/syscalls/syscall.tbl arch/s390/kernel/syscalls/syscall.tbl
158 check_2 tools/perf/arch/mips/entry/syscalls/syscall_n64.tbl arch/mips/kernel/syscalls/syscall_n64.t…
/tools/testing/selftests/powerpc/eeh/
Deeh-functions.sh62 echo 5000 > /sys/kernel/debug/powerpc/eeh_max_freezes
106 echo $dev >/sys/kernel/debug/powerpc/eeh_dev_break
111 echo $dev >/sys/kernel/debug/powerpc/eeh_dev_check
/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh140 echo ' ---' `date`: Starting kernel
181 echo " 3." Make the bare-metal kernel"'"s build system aware of your .config updates: >> $resdir/ba…
183 echo " 4." Build your bare-metal kernel. >> $resdir/bare-metal
184 echo " 5." Boot your bare-metal kernel with the following parameters: >> $resdir/bare-metal
190 echo " 8." Copy your bare-metal kernel"'"s .config file, overwriting this file: >> $resdir/bare-met…
199 echo kernel here: `head -n 1 $testid_txt | sed -e 's/^Build directory: //'` >> $resdir/bare-metal
201 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" $TOR…

123456789