Home
last modified time | relevance | path

Searched refs:simple (Results 1 – 25 of 27) sorted by relevance

12

/tools/testing/selftests/rcutorture/formal/srcu-cbmc/tests/
Dtest_script.sh46 SYNC_SRCU_MODE=${SYNC_SRCU_MODE:-simple}
50 simple) sync_srcu_mode_flags="-DUSE_SIMPLE_SYNC_SRCU" ;;
/tools/perf/Documentation/
Dperf-bench.txt38 'simple'::
39 This simple style is friendly for automated
42 % perf bench --format=simple sched pipe # specified simple
147 This uses a single thread simply doing getppid(2), which is a simple syscall where the result is not
154 Suite for evaluating performance of simple memory copy in various ways.
178 Suite for evaluating performance of simple memory set in various ways.
Djit-interface.txt1 perf supports a simple JIT interface to resolve symbols for dynamic code generated
Dperf-ftrace.txt6 perf-ftrace - simple wrapper for kernel's ftrace functionality
16 The 'perf ftrace' command is a simple wrapper of kernel's ftrace
Ddb-export.txt20 backward and forward compatibility, by following some simple rules:
Dperf-daemon.txt23 This command allows to run simple daemon process that starts and
Dperf-script-python.txt37 The syscall-counts script is a simple script, but demonstrates all the
330 writing a couple of very simple shell scripts and putting them in the
346 To have the script appear as a 'built-in' script, you write two simple
/tools/bootconfig/samples/
Dgood-simple.bconf1 # A good simple bootconfig
/tools/bpf/bpftool/Documentation/
Dbpftool.rst5 tool for inspection and simple manipulation of eBPF programs and maps
41 *bpftool* allows for inspection and simple modification of BPF objects
Dbpftool-link.rst5 tool for inspection and simple manipulation of eBPF links
Dbpftool-cgroup.rst5 tool for inspection and simple manipulation of eBPF progs
Dbpftool-map.rst5 tool for inspection and simple manipulation of eBPF maps
Dbpftool-gen.rst64 In addition to simple and reliable access to maps and
/tools/kvm/kvm_stat/
Dkvm_stat.service8 Type=simple
/tools/memory-model/Documentation/
Dsimple.txt2 memory-ordering lives simple, as is necessary for those whose domain
9 The options near the beginning of this list are quite simple. The idea
34 shared variables. A simple way to achieve this is to define a global lock
57 and release functions. After all, even simple non-production-quality
137 Although this APIs can be used in extremely complex ways, there are simple
141 The basic keep-things-simple rule for sequence locking is "do not write
143 readers, but it won't be so simple. For example, such writes will be
158 keep-things-simple rules for RCU are "do not write in read-side code"
204 If you want to keep things simple, use the initialization and read-out
DREADME12 o You are new to Linux-kernel concurrency: simple.txt
74 simple.txt
Drecipes.txt6 The first section covers simple special cases, the second section
14 This section presents two simple special cases, the first being where
65 about it too hard. And the basic rule is indeed quite simple: Any CPU that
468 well as simple and powerful, at least as memory-ordering mechanisms go.
Dexplanation.txt88 memory locations, things aren't so simple.
99 Here is a simple example to illustrate the basic concepts. Consider
110 (the reason for using WRITE_ONCE() and READ_ONCE() instead of simple
161 Some nontrivial predictions are nonetheless quite simple. For
438 simple example:
453 a write. Here's another simple example:
1224 An equally simple case involves two loads of the same location that
1250 Less trivial examples of prop all involve fences. Unlike the simple
1460 Here is a simple example of RCU in action:
1566 We'll consider just a very simple case:
[all …]
Dordering.txt288 to a simple load instruction followed by a simple store instruction.
/tools/testing/selftests/bpf/progs/
Dbtf_dump_test_case_syntax.c158 struct struct_simple simple; member
/tools/testing/selftests/tc-testing/
DTODO.txt31 - super simple test case example using ls, touch, etc
/tools/thermal/tmon/
DREADME5 Increasingly, Linux is running on thermally constrained devices. The simple
/tools/testing/selftests/futex/
DREADME25 o The build system shall remain as simple as possible, avoiding any archive or
/tools/testing/selftests/arm64/signal/
DREADME34 they are just fired using some simple included assembly trampoline code.
/tools/power/pm-graph/
DREADME105 If you're using a kernel older than 3.11-rc2, the following simple
334 Run a simple mem suspend:

12