Home
last modified time | relevance | path

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

12345678910

/tools/testing/selftests/android/
DREADME5 $ kernel/tests/tools/run_test_only.sh -t selftests -s <serial_number>
8 $ kernel/tests/tools/launch_cvd.sh
14 * Build kernel and launch a virtual device from a specific platform build:
15 $ kernel/tests/tools/launch_cvd.sh -pb \
19 $ kernel/tests/tools/run_test_only.sh \
23 $ kernel/tests/tools/launch_cvd.sh -h
24 $ kernel/tests/tools/run_test_only.sh -h
/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.sh58 DYNAMIC_DEBUG=$(grep '^kernel/livepatch' /sys/kernel/debug/dynamic_debug/control | \
60 FTRACE_ENABLED=$(sysctl --values kernel.ftrace_enabled)
65 echo -n "$DYNAMIC_DEBUG" > /sys/kernel/debug/dynamic_debug/control
68 sysctl kernel.ftrace_enabled="$FTRACE_ENABLED" &> /dev/null
73 cat <<-EOF > /sys/kernel/debug/dynamic_debug/control
74 file kernel/livepatch/* +p
86 local err=$(sysctl -q kernel.ftrace_enabled="$1" 2>&1)
87 local result=$(sysctl --values kernel.ftrace_enabled)
250 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
32 Test kernel modules are built before running the livepatch selftests. The
38 To run the livepatch selftests, from the top of the kernel source tree:
52 check_result(). The latter function greps the kernel's ring buffer for
/tools/testing/selftests/powerpc/security/
Dmitigation-patching.sh31 cd /sys/kernel/debug/powerpc || rc=1
37 tainted=$(cat /proc/sys/kernel/tainted)
47 if [[ -f /sys/kernel/debug/powerpc/$m ]]
71 tainted=$(cat /proc/sys/kernel/tainted)
/tools/include/uapi/
DREADME1 Why we want a copy of kernel headers in tools?
4 There used to be no copies, with tools/ code using kernel headers
5 directly. From time to time tools/perf/ broke due to legitimate kernel
40 the original kernel headers, that will be done later, when
47 was pushed back on from the kernel side, when tooling modified the
48 headers and broke them accidentally for kernel builds.
52 notification mechanism to look at new kernel side changes.
56 - A software-enforced copy-on-write mechanism of kernel headers to
58 kernel headers get modified:
66 The tooling policy is to always pick up the kernel side headers as-is,
[all …]
/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.
14 o You are new to Linux-kernel concurrency: simple.txt
16 o You have some background in Linux-kernel concurrency, and would
18 that the Linux kernel provides: ordering.txt
22 o You are familiar with the Linux-kernel concurrency primitives
29 o You are familiar with Linux-kernel concurrency, and would
41 o You are familiar with Linux-kernel concurrency and the use of
44 o You are familiar with Linux-kernel concurrency and the use
66 Quick-reference guide to the Linux-kernel memory model.
[all …]
/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.
37 --kernel-maps::
38 Show buildid, start/end text address, and path of running kernel and
Dguest-files.txt5 kernel symbols. Users copy it out from guest OS.
9 kernel module information. Users copy it out from guest OS.
12 Guest OS kernel vmlinux.
Dperf-intel-pt.txt69 To also trace kernel space presents a problem, namely kernel self-modifying
70 code. A fairly good kernel image is available in /proc/kcore but to get an
228 The Intel PT kernel driver creates a new PMU for Intel PT. PMU events are
246 passed to the kernel by the perf_event_open system call. They correspond to bit
277 k kernel
580 The difference between full trace and snapshot from the kernel's perspective is
597 (or if /proc/sys/kernel/perf_event_paranoid < 0), 128KiB for unprivileged users.
619 (or if /proc/sys/kernel/perf_event_paranoid < 0), 128KiB for unprivileged users.
624 512KiB (actually /proc/sys/kernel/perf_event_mlock_kb minus 1 page) per cpu
780 Unless /proc/sys/kernel/perf_event_paranoid is set to -1, unprivileged users
[all …]
/tools/perf/tests/shell/common/
Dinit.sh122 test -e /sys/kernel/debug/tracing/kprobe_events
127 test -e /sys/kernel/debug/tracing/uprobe_events
132 echo 0 > /sys/kernel/debug/tracing/events/enable
133 check_kprobes_available && echo > /sys/kernel/debug/tracing/kprobe_events
134 check_uprobes_available && echo > /sys/kernel/debug/tracing/uprobe_events
/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/testing/selftests/bpf/
Dtest_ftrace.sh3 if [[ -e /sys/kernel/tracing/trace ]]; then
4 TR=/sys/kernel/tracing/
6 TR=/sys/kernel/debug/tracing/
/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
71 Example litmus tests may be found in the Linux-kernel source tree:
79 https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git/tree/CodeSamples/formal/herd
80 https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git/tree/CodeSamples/formal/litmus
93 $ herd7 -conf linux-kernel.cfg litmus-tests/SB+fencembonceonces.litmus
[all …]
/tools/testing/selftests/net/netfilter/
Dbr_netfilter_queue.sh7 read t < /proc/sys/kernel/tainted
9 echo SKIP: kernel is tainted
76 read t < /proc/sys/kernel/tainted
78 echo PASS: kernel not tainted
80 echo ERROR: kernel is tainted
/tools/testing/kunit/android/
DREADME6 "no trim" kernel (e.g. add `--notrim` to bazel build command).
9 $ kernel/tests/tools/run_test_only.sh -t kunit -s <serial_number> -td <test_dir>
15 $ kernel/tests/tools/launch_cvd.sh
21 * Build kernel and launch a virtual device from a specific platform build:
22 $ kernel/tests/tools/launch_cvd.sh -pb \
26 $ kernel/tests/tools/run_test_only.sh \
30 $ kernel/tests/tools/launch_cvd.sh -h
31 $ kernel/tests/tools/run_test_only.sh -h
51 $ mount -t debugfs debugfs /sys/kernel/debug
59 $ cat /sys/kernel/debug/kunit/<test name>/results
[all …]
/tools/debugging/
DMakefile8 TARGET = kernel-chktaint
14 install: kernel-chktaint
/tools/bpf/bpftool/Documentation/
Dbpftool-feature.rst7 tool for inspection of eBPF-related parameters for Linux kernel or net device
30 | *COMPONENT* := { **kernel** | **dev** *NAME* }
35 bpftool feature probe [kernel] [full] [macros [prefix *PREFIX*]]
36 Probe the running kernel and dump a number of eBPF-related parameters, such
41 () and **bpf_trace_printk**\() helpers which print warnings to kernel logs.
51 Keyword **kernel** can be omitted. If no probe target is specified, probing
52 the kernel is the default behaviour.
67 probing the kernel.
Dbpftool-iter.rst35 A bpf iterator combines a kernel iterating of particular kernel data (e.g.,
36 tasks, bpf_maps, etc.) and a bpf program called for each kernel data object
37 (e.g., one task, one bpf_map, etc.). User space can *read* kernel iterator
46 program in kernel to run with each map element, do checking, filtering,
/tools/testing/selftests/pstore/
Dpstore_crash_test16 echo 1 > /proc/sys/kernel/sysrq
18 echo 3 > /proc/sys/kernel/panic
/tools/testing/selftests/kvm/x86_64/
Dnx_huge_pages_test.sh14 HUGE_PAGES=$(cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages)
43 sudo_echo "$(( $HUGE_PAGES + 3 ))" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
67 sudo_echo "$HUGE_PAGES" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
/tools/tracing/rtla/
DREADME.txt5 rtla leverages kernel tracing capabilities to provide precise information
19 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
24 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git
/tools/verification/rv/
DREADME.txt22 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
27 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git
36 For further information, please see rv manpage and the kernel documentation:

12345678910