Home
last modified time | relevance | path

Searched refs:one (Results 1 – 25 of 26) sorted by relevance

12

/tools/testing/selftests/rcutorture/doc/
DTREE_RCU-kconfig.txt8 CONFIG_DEBUG_OBJECTS_RCU_HEAD -- Do one.
10 CONFIG_HZ_PERIODIC -- Do one.
12 CONFIG_NO_HZ_FULL -- Do two, one with CONFIG_NO_HZ_FULL_SYSIDLE.
13 CONFIG_NO_HZ_FULL_SYSIDLE -- Do one.
16 CONFIG_PROVE_RCU -- Do all but one under CONFIG_PROVE_LOCKING.
17 CONFIG_RCU_BOOST -- one of TREE_PREEMPT_RCU.
19 CONFIG_RCU_CPU_STALL_INFO -- do one with and without _VERBOSE.
20 CONFIG_RCU_CPU_STALL_VERBOSE -- do one with and without _INFO.
22 CONFIG_RCU_FANOUT_EXACT -- Do one.
23 CONFIG_RCU_FANOUT_LEAF -- Do one non-default.
[all …]
Drcu-test-image.txt1 This document describes one way to created the rcu-test-image file
Dinitrd.txt1 This document describes one way to create the initrd directory hierarchy
/tools/perf/tests/
Dsample-parsing.c64 COMP(read.one.value); in samples_same()
74 COMP(read.one.id); in samples_same()
203 sample.read.one.value = 0x08789faeb786aa87ULL; in do_test()
204 sample.read.one.id = 99; in do_test()
/tools/perf/
Ddesign.txt19 There's one file descriptor per virtual counter used.
123 A counter of type PERF_TYPE_SOFTWARE will count one of the available
150 counters. A "counting" counter is one that is used for counting the
169 Using these additional values one can establish the overcommit ratio for a
170 particular counter allowing one to take the round-robin scheduling effect
174 A "sampling" counter is one that is set up to generate an interrupt
262 counter group has one counter which is the group "leader". The leader
401 Normally a notification is generated for every page filled, however one can
402 additionally set perf_event_attr.wakeup_events to generate one every
Dbuiltin-lock.c206 static int lock_stat_key_ ## member(struct lock_stat *one, \
209 return one->member > two->member; \
218 static int lock_stat_key_wait_time_min(struct lock_stat *one, in SINGLE_KEY()
221 u64 s1 = one->wait_time_min; in SINGLE_KEY()
Dbuiltin-kvm.c439 static int compare_kvm_event_ ## func(struct kvm_event *one, \
442 return get_event_ ##func(one, vcpu) > \
/tools/perf/Documentation/
Dperf-mem.txt37 one sample per line.
Dperf-annotate.txt64 --tui:: Use the TUI interface. Use of --tui requires a tty, if one is not
Dperf-probe.txt129 'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is t…
170 …o can give several rules combined with "&" or "|", and fold those rules as one rule by using "(" "…
188 this will add one or more probes which has the name start with "schedule".
Dperf-script-python.txt170 Following those are the 'event handler' functions generated one for
172 the form subsystem__event_name, and contain named parameters, one for
173 each field in the event; in this case, there's only one event,
349 scripts, one for recording and one for 'reporting'.
Dperf-list.txt22 Events can optionally have a modifier by appending a colon and one or
Dperf-report.txt202 function into one place in the call-graph tree.
211 requires a tty, if one is not present, as when piping to other
Dperf-kvm.txt82 typically, sshfs. For example, start 2 guest os. The one's pid is 8888
Dperf-top.txt184 function into one place in the call-graph tree.
Dperf-record.txt190 The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
/tools/usb/usbip/
DINSTALL21 It may also create one or more `.h' files containing system-dependent
91 You can compile the package for more than one kind of computer at the
98 With a non-GNU `make', it is safer to compile the package for one
100 installed the package for one architecture, use `make distclean' before
154 where SYSTEM can have one of these forms:
/tools/perf/util/
Devent.h118 struct sample_read_value one; member
Devsel.c1403 data->read.one.value = *array; in perf_evsel__parse_sample()
1434 data->read.one.id = *array; in perf_evsel__parse_sample()
1722 *array = sample->read.one.value; in perf_event__synthesize_sample()
1742 *array = sample->read.one.id; in perf_event__synthesize_sample()
Dsession.c642 sample->read.one.id, sample->read.one.value); in sample_read__printf()
797 &sample->read.one, machine); in perf_session__deliver_sample()
/tools/power/cpupower/po/
Dde.po119 "only one of: -t, -l, -m are allowed\n"
525 "You can't specify more than one --cpu parameter and/or\n"
526 "more than one output-specific argument\n"
664 "At least one parameter out of -f/--freq, -d/--min, -u/--max, and\n"
943 msgid "You can't specify more than one output-specific argument\n"
Dfr.po119 "only one of: -t, -l, -m are allowed\n"
517 "You can't specify more than one --cpu parameter and/or\n"
518 "more than one output-specific argument\n"
653 "At least one parameter out of -f/--freq, -d/--min, -u/--max, and\n"
930 msgid "You can't specify more than one output-specific argument\n"
Dcs.po122 "only one of: -t, -l, -m are allowed\n"
517 "You can't specify more than one --cpu parameter and/or\n"
518 "more than one output-specific argument\n"
653 "At least one parameter out of -f/--freq, -d/--min, -u/--max, and\n"
928 msgid "You can't specify more than one output-specific argument\n"
Dit.po119 "only one of: -t, -l, -m are allowed\n"
520 "You can't specify more than one --cpu parameter and/or\n"
521 "more than one output-specific argument\n"
661 "At least one parameter out of -f/--freq, -d/--min, -u/--max, and\n"
938 msgid "You can't specify more than one output-specific argument\n"
Dpt.po117 "only one of: -t, -l, -m are allowed\n"
522 "You can't specify more than one --cpu parameter and/or\n"
523 "more than one output-specific argument\n"
663 "At least one parameter out of -f/--freq, -d/--min, -u/--max, and\n"
940 msgid "You can't specify more than one output-specific argument\n"

12