| /linux/arch/mips/mm/ |
| H A D | init.c | 320 } recorded = { { { 0 } }, 0 }; in maar_init() local
334 if (recorded.used) { in maar_init()
335 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init()
336 BUG_ON(used != recorded.used); in maar_init()
350 if (recorded.used) in maar_init()
387 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init()
388 recorded.cfgs[recorded.used].lower = lower; in maar_init()
389 recorded.cfgs[recorded.used].upper = upper; in maar_init()
390 recorded.cfgs[recorded.used].attrs = attr; in maar_init()
391 recorded.used++; in maar_init()
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| H A 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
|
| H A D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| H A 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/arch/microblaze/kernel/ |
| H A 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/Documentation/core-api/ |
| H A 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/Documentation/filesystems/ext4/ |
| H A 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/tools/perf/tests/shell/base_report/ |
| H A D | stderr-whitelist.txt | 4 \d+ out of order events recorded.
|
| /linux/Documentation/trace/ |
| H A 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
|
| H A D | eprobetrace.rst | 16 recorded in the trace event.
77 The basic usage of eprobes is to limit the data that is being recorded into
101 An eprobe can limit what gets recorded. Note, it does not help in performance,
102 as all the fields are recorded in a temporary buffer to process the eprobe.
142 If a specific system call is to be recorded but the syscalls events are not
|
| H A 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
374 that will be recorded into the ring buffer to hold this data.
471 is recorded into the buffer and not the string itself. This prevents
478 Only the pid of the task is recorded in a trace event unless
525 Whenever an event is recorded into the ring buffer, a
667 events can be recorded in different buffers.
858 See tracing_max_latency. When a new max is recorded,
1392 When set, a stack trace is recorded after any trace event
1393 is recorded.
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A 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
|
| H A D | callchain-overhead-calculation.txt | 44 Suppose all samples are recorded in 'foo' and 'bar' only. When it's
45 recorded with callchains the output will show something like below
|
| H A 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)
234 perf inject to insert a perf.data file recorded inside a virtual machine into
235 a perf.data file recorded on the host at the same time.
255 CYCLES: the number of cycles that have elapsed since the last branch was recorded
265 sample was recorded with perf record -b or -j any.
|
| H A 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
105 To analyse recorded profile in aggregate mode
|
| H A 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/Documentation/locking/ |
| H A 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/Documentation/devicetree/ |
| H A D | changesets.rst | 27 All the change operations are recorded in the of_changeset 'entries'
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-fwrite.rst | 38 digitally recorded Transport Stream. Matching filters have to be defined
|
| H A D | dmx-fopen.rst | 61 A recorded Transport Stream is replayed by writing to this device.
|
| /linux/Documentation/driver-api/iio/ |
| H A D | triggered-buffers.rst | 64 stores it in the internal buffer together with the timestamp recorded in the
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-fm-tx.rst | 66 then the audio was recorded as stereo.
72 recorded using an artificial head.
|
| /linux/tools/perf/ |
| H A 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/Documentation/userspace-api/ |
| H A 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
|