Home
last modified time | relevance | path

Searched refs:four (Results 1 – 15 of 15) sorted by relevance

/tools/testing/selftests/bpf/progs/
Dtest_sockmap_kern.h237 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local
257 start_pop = bpf_map_lookup_elem(&sock_bytes, &four); in bpf_prog4()
267 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
292 start_pop = bpf_map_lookup_elem(&sock_bytes, &four); in bpf_prog6()
348 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local
367 start_pop = bpf_map_lookup_elem(&sock_bytes, &four); in bpf_prog10()
/tools/bpf/
DMakefile37 FEATURE_TESTS = libbfd disassembler-four-args
38 FEATURE_DISPLAY = libbfd disassembler-four-args
56 ifeq ($(feature-disassembler-four-args), 1)
/tools/build/
DMakefile.feature71 disassembler-four-args \
130 disassembler-four-args
/tools/bpf/bpftool/
DMakefile64 FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap \
66 FEATURE_DISPLAY = libbfd disassembler-four-args zlib libcap \
85 ifeq ($(feature-disassembler-four-args), 1)
/tools/testing/selftests/resctrl/
DREADME34 A test case has four stages:
/tools/build/feature/
DMakefile19 test-disassembler-four-args.bin \
235 $(OUTPUT)test-disassembler-four-args.bin:
/tools/perf/Documentation/
Dtopdown.txt147 The value reported by read_metrics() contains four 8 bit fields
149 All four fields add up to 0xff (= 100%)
Dperf-list.txt240 For example Intel Core CPUs typically have four generic performance counters
Dperf-trace.txt325 Trace the next two sched:sched_switch events, four block:*_plug events, the
Dperf-config.txt253 For example, let's see a part of a program. There're four lines.
/tools/perf/
DMakefile.config283 FEATURE_CHECK_LDFLAGS-disassembler-four-args = -lbfd -lopcodes -ldl
842 FEATURE_CHECK_LDFLAGS-disassembler-four-args += -liberty -ldl
846 FEATURE_CHECK_LDFLAGS-disassembler-four-args += -liberty -lz -ldl
849 $(call feature_check,disassembler-four-args)
959 ifeq ($(feature-disassembler-four-args), 1)
/tools/usb/usbip/
DREADME13 Whole project consists of four parts:
/tools/testing/selftests/tc-testing/
DREADME79 A test case has four stages:
/tools/power/pm-graph/
DREADME449 can include up to four pieces of info: The function name, a format string,
524 to four pieces of info: The function name, a format string, an argument list,
/tools/memory-model/Documentation/
Dexplanation.txt581 requirement takes the form of four coherency rules:
864 system obey the four coherency rules.
903 You can check that the four coherency rules imply that the rf, co, fr,
918 true: This LKMM axiom implies that the four coherency rules are