| /Linux-v5.10/arch/mips/mm/ |
| D | init.c | 322 } recorded = { { { 0 } }, 0 }; in maar_init() local
336 if (recorded.used) { in maar_init()
337 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init()
338 BUG_ON(used != recorded.used); in maar_init()
352 if (recorded.used) in maar_init()
389 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init()
390 recorded.cfgs[recorded.used].lower = lower; in maar_init()
391 recorded.cfgs[recorded.used].upper = upper; in maar_init()
392 recorded.cfgs[recorded.used].attrs = attr; in maar_init()
393 recorded.used++; in maar_init()
|
| /Linux-v5.10/arch/microblaze/kernel/ |
| D | ftrace.c | 102 static unsigned int recorded; /* if save was or not */ variable
133 if (recorded == 0) { in ftrace_make_nop()
134 recorded = 1; in ftrace_make_nop()
|
| /Linux-v5.10/Documentation/core-api/ |
| D | errseq.rst | 18 Note that there is a risk of collisions if new errors are being recorded
23 recorded. That allows us to avoid bumping the counter if no one has
24 sampled it since the last time an error was recorded.
107 return 0, until another error is recorded, at which point it's reported
112 recorded.
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-sched.txt | 24 was recorded (aliased to 'perf script' for now).
26 'perf sched replay' to simulate the workload that was recorded
30 of the workload as it occurred when it was recorded - and can repeat
|
| D | itrace.txt | 8 o synthesize other events recorded due to the use
42 On x86, note that G and L work poorly when data has been recorded with
|
| D | callchain-overhead-calculation.txt | 43 Suppose all samples are recorded in 'foo' and 'bar' only. When it's
44 recorded with callchains the output will show something like below
|
| D | perf-script.txt | 19 This command reads the input file and displays the trace recorded.
24 recorded.
35 recorded using the -a (system-wide) 'perf record' option.
50 not specified, the events are recorded using the -a (system-wide)
225 sample was recorded with perf record -b or -j any.
|
| D | perf-intel-pt.txt | 35 or "branches" events had been recorded. Presently 3 tools support this:
680 continue to be recorded while intel_pt is disabled. That is important to ensure
873 "Instructions" events look like they were recorded by "perf record -e
876 "Branches" events look like they were recorded by "perf record -e branches". "c"
889 recorded only if the "ptw" config term was used. Refer to the config terms
895 packets. While CBR packets are always recorded when tracing is enabled, power
896 event packets are recorded only if the "pwr_evt" config term was used. Refer to
910 "exstop" indicates execution stopped and whether the IP was recorded
|
| D | perf-report.txt | 15 This command displays the performance counter profile information recorded
41 Show per-thread event counters. The input data file should be recorded
198 information recorded. The pattern is in the extended regex format and
265 and will be sorted on the data. It requires callchains are recorded.
|
| /Linux-v5.10/Documentation/filesystems/ext4/ |
| D | ifork.rst | 65 be recorded without the use of extra metadata blocks.
67 The extent tree header is recorded in ``struct ext4_extent_header``,
104 recorded as ``struct ext4_extent_idx``, and are 12 bytes long:
133 Leaf nodes of the extent tree are recorded as ``struct ext4_extent``,
|
| /Linux-v5.10/Documentation/trace/ |
| D | mmiotrace.rst | 123 an event that is recorded into the trace log. Note that ISA range mappings
126 MMIO accesses are recorded via page faults. Just before __ioremap() returns,
166 zero if it is not recorded. PID is always zero as tracing MMIO accesses
182 - replaying MMIO logs, i.e., re-executing the recorded writes
|
| D | ftrace.rst | 170 recorded if the latency is greater than the value in this file
173 By echoing in a time into this file, no latency will be recorded
396 is recorded into the buffer and not the string itself. This prevents
403 Only the pid of the task is recorded in a trace event unless
450 Whenever an event is recorded into the ring buffer, a
580 events can be recorded in different buffers.
749 See tracing_max_latency. When a new max is recorded,
1236 When set, a stack trace is recorded after any trace event
1237 is recorded.
1255 When set, a stack trace is recorded after every
[all …]
|
| /Linux-v5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-field_print.txt | 24 These functions print recorded field's data, according to the field's type.
26 The _tep_print_field()_ function extracts from the recorded raw _data_ value of
|
| D | libtraceevent-cpus.txt | 31 data recorded.
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 15 from the start of the recorded sample (in ms)
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| /Linux-v5.10/Documentation/devicetree/ |
| D | changesets.rst | 27 All the change operations are recorded in the of_changeset 'entries'
|
| /Linux-v5.10/Documentation/locking/ |
| D | lockstat.rst | 145 Lines 09-12 show the first 4 recorded contention points (the code
146 which tries to get the lock) and lines 14-17 show the first 4 recorded
|
| /Linux-v5.10/Documentation/userspace-api/media/dvb/ |
| D | dmx-fwrite.rst | 38 digitally recorded Transport Stream. Matching filters have to be defined
|
| D | dmx-fopen.rst | 61 A recorded Transport Stream is replayed by writing to this device.
|
| /Linux-v5.10/Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 64 stores it in the internal buffer together with the timestamp recorded in the
|
| /Linux-v5.10/tools/memory-model/scripts/ |
| D | README | 11 the results against the expected results recorded in the
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 65 then the audio was recorded as stereo.
71 recorded using an artificial head.
|
| /Linux-v5.10/tools/perf/ |
| D | design.txt | 176 has irq_period > 0. The record_type controls what data is recorded on each
192 Such (and other) events will be recorded in a ring-buffer, which is
232 these events are recorded in the ring-buffer (see below).
235 This too is recorded in the ring-buffer (see below).
|
| /Linux-v5.10/Documentation/sound/cards/ |
| D | bt87x.rst | 40 recorded data is not right, try to specify the ``digital_rate`` option with
|
