/linux-6.12.1/arch/mips/mm/ |
D | init.c | 328 } recorded = { { { 0 } }, 0 }; in maar_init() local 342 if (recorded.used) { in maar_init() 343 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init() 344 BUG_ON(used != recorded.used); in maar_init() 358 if (recorded.used) in maar_init() 395 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init() 396 recorded.cfgs[recorded.used].lower = lower; in maar_init() 397 recorded.cfgs[recorded.used].upper = upper; in maar_init() 398 recorded.cfgs[recorded.used].attrs = attr; in maar_init() 399 recorded.used++; in maar_init()
|
/linux-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/tools/perf/tests/shell/base_report/ |
D | stderr-whitelist.txt | 4 \d+ out of order events recorded.
|
/linux-6.12.1/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-6.12.1/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
|
/linux-6.12.1/tools/perf/Documentation/ |
D | itrace.txt | 9 o synthesize other events recorded due to the use 49 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-amd-ibs.txt | 42 IBS gives samples with precise IP, i.e. the IP recorded with IBS sample has 43 no skid. Whereas the IP recorded by regular core PMU will have some skid 96 To analyse recorded profile in aggregate mode
|
D | perf-sched.txt | 44 was recorded (aliased to 'perf script' for now). 46 'perf sched replay' to simulate the workload that was recorded 50 of the workload as it occurred when it was recorded - and can repeat
|
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) 232 perf inject to insert a perf.data file recorded inside a virtual machine into 233 a perf.data file recorded on the host at the same time. 254 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.
|
/linux-6.12.1/Documentation/devicetree/bindings/mfd/ |
D | twl4030-audio.txt | 15 from the start of the recorded sample (in ms)
|
/linux-6.12.1/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-6.12.1/Documentation/devicetree/ |
D | changesets.rst | 27 All the change operations are recorded in the of_changeset 'entries'
|
/linux-6.12.1/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-6.12.1/Documentation/driver-api/iio/ |
D | triggered-buffers.rst | 64 stores it in the internal buffer together with the timestamp recorded in the
|
/linux-6.12.1/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-6.12.1/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-6.12.1/Documentation/userspace-api/ |
D | perf_ring_buffer.rst | 252 thread *T1* is running, the perf events will be recorded into the ring 254 disabled, thus no trace data will be recorded into the ring buffer. 276 ``––per–thread`` are specified together, the samples are recorded only when 332 are monitored during the running state and the samples are recorded into 400 stored in the ``perf_buffer::watermark``. When a sample is recorded into 525 the recorded data from the ring buffer, and then updates the buffer's 649 the hardware trace data will be recorded into the dedicated buffers for
|