| /Linux-v4.19/arch/mips/mm/ |
| D | init.c | 302 } recorded = { { { 0 } }, 0 }; in maar_init() local
316 if (recorded.used) { in maar_init()
317 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init()
318 BUG_ON(used != recorded.used); in maar_init()
332 if (recorded.used) in maar_init()
363 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init()
364 recorded.cfgs[recorded.used].lower = lower; in maar_init()
365 recorded.cfgs[recorded.used].upper = upper; in maar_init()
366 recorded.cfgs[recorded.used].attrs = attr; in maar_init()
367 recorded.used++; in maar_init()
|
| /Linux-v4.19/arch/microblaze/kernel/ |
| D | ftrace.c | 113 static unsigned int recorded; /* if save was or not */ variable
144 if (recorded == 0) { in ftrace_make_nop()
145 recorded = 1; in ftrace_make_nop()
|
| /Linux-v4.19/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-v4.19/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 | 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)
216 sample was recorded with perf record -b or -j any.
|
| D | intel-pt.txt | 26 or "branches" events had been recorded. Presently 3 tools support this:
543 continue to be recorded while intel_pt is disabled. That is important to ensure
733 "Instructions" events look like they were recorded by "perf record -e
736 "Branches" events look like they were recorded by "perf record -e branches". "c"
749 recorded only if the "ptw" config term was used. Refer to the config terms
755 packets. While CBR packets are always recorded when tracing is enabled, power
756 event packets are recorded only if the "pwr_evt" config term was used. Refer to
770 "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
187 information recorded. The pattern is in the extended regex format and
254 and will be sorted on the data. It requires callchains are recorded.
|
| D | examples.txt | 189 Or you can annotate the recorded 'git gc' run on a per symbol basis
|
| D | perf-kvm.txt | 40 recorded via perf kvm record.
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| 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``,
|
| D | inodes.rst | 465 record size is recorded in the superblock as ``s_inode_size``. The
467 128-byte ext2 inode is recorded in the ``i_extra_isize`` field for each
493 Four timestamps are recorded in the lower 128 bytes of the inode
|
| /Linux-v4.19/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 | 165 recorded if the latency is greater than the value in this file
168 By echoing in a time into this file, no latency will be recorded
357 is recorded into the buffer and not the string itself. This prevents
364 Only the pid of the task is recorded in a trace event unless
411 Whenever an event is recorded into the ring buffer, a
538 events can be recorded in different buffers.
707 See tracing_max_latency. When a new max is recorded,
1153 When set, a stack trace is recorded after any trace event
1154 is recorded.
1172 When set, a stack trace is recorded after every
[all …]
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| /Linux-v4.19/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 15 from the start of the recorded sample (in ms)
|
| /Linux-v4.19/Documentation/devicetree/ |
| D | changesets.txt | 21 All the change operations are recorded in the of_changeset 'entries'
|
| /Linux-v4.19/Documentation/locking/ |
| D | lockstat.txt | 124 Lines 09-12 show the first 4 recorded contention points (the code
125 which tries to get the lock) and lines 14-17 show the first 4 recorded
|
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | dmx-fwrite.rst | 39 digitally recorded Transport Stream. Matching filters have to be defined
|
| D | dmx-fopen.rst | 63 A recorded Transport Stream is replayed by writing to this device.
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | hugetlb.txt | 31 hugetlb.<hugepagesize>.max_usage_in_bytes # show max "hugepagesize" hugetlb usage recorded
|
| /Linux-v4.19/Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 64 stores it in the internal buffer together with the timestamp recorded in the
|
| /Linux-v4.19/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
228 these events are recorded in the ring-buffer (see below).
231 This too is recorded in the ring-buffer (see below).
|
| /Linux-v4.19/Documentation/sound/cards/ |
| D | bt87x.rst | 40 recorded data is not right, try to specify the ``digital_rate`` option with
|
| /Linux-v4.19/Documentation/accounting/ |
| D | taskstats-struct.txt | 93 * xxx_count is the number of delay values recorded
|
