| /Linux-v6.6/arch/mips/mm/ |
| D | init.c | 326 } recorded = { { { 0 } }, 0 }; in maar_init() local
340 if (recorded.used) { in maar_init()
341 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init()
342 BUG_ON(used != recorded.used); in maar_init()
356 if (recorded.used) in maar_init()
393 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init()
394 recorded.cfgs[recorded.used].lower = lower; in maar_init()
395 recorded.cfgs[recorded.used].upper = upper; in maar_init()
396 recorded.cfgs[recorded.used].attrs = attr; in maar_init()
397 recorded.used++; in maar_init()
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-class-fc_host | 6 events recorded by the F_Port, reported using fabric
14 events recorded by the F_Port/Nx_Port, reported using fabric
22 recorded by the F_Port/Nx_Port, reported using fabric
|
| D | sysfs-class-fc_remote_ports | 6 events recorded by the F_Port/Nx_Port, reported using fabric
14 events recorded by the F_Port/Nx_Port, reported using fabric
22 recorded by the F_Port/Nx_Port, reported using fabric
|
| D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| D | sysfs-firmware-acpi | 28 suspend_start_ns: Timer value recorded at the previous
31 suspend_end_ns: Timer value recorded at the previous
40 resume_prev_ns: Timer recorded at the end of the previous
|
| /Linux-v6.6/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-v6.6/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-v6.6/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-v6.6/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 | 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 | itrace.txt | 9 o synthesize other events recorded due to the use
48 On x86, note that G and L work poorly when data has been recorded with
|
| 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)
231 perf inject to insert a perf.data file recorded inside a virtual machine into
232 a perf.data file recorded on the host at the same time.
253 sample was recorded with perf record -b or -j any.
|
| D | perf-inject.txt | 96 Insert events from a perf.data file recorded in a virtual machine at
97 the same time as the input perf.data file was recorded on the host.
|
| D | perf-arm-spe.txt | 41 Program counter, PMU events, timings and data addresses related to the operation are recorded.
65 recorded file is opened with 'perf report' or 'perf script' does the decoding happen. When decoding
|
| /Linux-v6.6/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
427 is recorded into the buffer and not the string itself. This prevents
434 Only the pid of the task is recorded in a trace event unless
481 Whenever an event is recorded into the ring buffer, a
623 events can be recorded in different buffers.
792 See tracing_max_latency. When a new max is recorded,
1291 When set, a stack trace is recorded after any trace event
1292 is recorded.
1310 When set, a stack trace is recorded after every
[all …]
|
| /Linux-v6.6/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 15 from the start of the recorded sample (in ms)
|
| /Linux-v6.6/Documentation/devicetree/ |
| D | changesets.rst | 27 All the change operations are recorded in the of_changeset 'entries'
|
| /Linux-v6.6/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-v6.6/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-v6.6/Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 64 stores it in the internal buffer together with the timestamp recorded in the
|
| /Linux-v6.6/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-v6.6/tools/perf/ |
| D | design.txt | 179 has irq_period > 0. The record_type controls what data is recorded on each
195 Such (and other) events will be recorded in a ring-buffer, which is
235 these events are recorded in the ring-buffer (see below).
238 This too is recorded in the ring-buffer (see below).
|
| /Linux-v6.6/Documentation/sound/cards/ |
| D | bt87x.rst | 40 recorded data is not right, try to specify the ``digital_rate`` option with
|
