| /linux-4.4.14/arch/mips/mm/ |
| D | init.c | 299 } recorded = { { { 0 } }, 0 }; in maar_init() local
313 if (recorded.used) { in maar_init()
314 used = maar_config(recorded.cfgs, recorded.used, num_maars / 2); in maar_init()
315 BUG_ON(used != recorded.used); in maar_init()
329 if (recorded.used) in maar_init()
360 if (used <= ARRAY_SIZE(recorded.cfgs)) { in maar_init()
361 recorded.cfgs[recorded.used].lower = lower; in maar_init()
362 recorded.cfgs[recorded.used].upper = upper; in maar_init()
363 recorded.cfgs[recorded.used].attrs = attr; in maar_init()
364 recorded.used++; in maar_init()
|
| /linux-4.4.14/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-4.4.14/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)
|
| D | perf-report.txt | 15 This command displays the performance counter profile information recorded
37 Show per-thread event counters. The input data file should be recorded
150 information recorded. The pattern is in the exteneded regex format and
210 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.
|
| D | intel-pt.txt | 26 or "branches" events had been recorded. Presently 3 tools support this:
504 continue to be recorded while intel_pt is disabled. That is important to ensure
676 "Instructions" events look like they were recorded by "perf record -e
679 "Branches" events look like they were recorded by "perf record -e branches". "c"
|
| D | perf-script-python.txt | 104 That single stream will be recorded in a file in the current directory
181 mean either that the record step recorded event types that it wasn't
452 Traces meant to be processed using a script should be recorded with
|
| D | perf-script-perl.txt | 54 Traces meant to be processed using a script should be recorded with
|
| D | perf-record.txt | 263 Enable weightened sampling. An additional weight is recorded per sample and can be
|
| /linux-4.4.14/Documentation/trace/ |
| D | mmiotrace.txt | 104 an event that is recorded into the trace log. Note that ISA range mappings
107 MMIO accesses are recorded via page faults. Just before __ioremap() returns,
147 zero if it is not recorded. PID is always zero as tracing MMIO accesses
162 - replaying MMIO logs, i.e., re-executing the recorded writes
|
| D | ftrace.txt | 134 A new max trace will only be recorded if the
282 does this), only a pointer to the string is recorded into the buffer
290 Only the pid of the task is recorded in a trace event unless
321 Whenever an event is recorded into the ring buffer, a
406 events can be recorded in different buffers.
515 See tracing_max_latency. When a new max is recorded,
800 itself. When a trace is recorded, so is the stack
1452 not recorded because the tracer only records one worst case and
1496 is before the actual "switch", we stop the tracing when the recorded task
1500 Notice that the recorded task is 'sleep' with the PID of 2389
[all …]
|
| D | tracepoint-analysis.txt | 220 data must be recorded. At the time of writing, this required root:
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 15 from the start of the recorded sample (in ms)
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 21 All the change operations are recorded in the of_changeset 'entries'
|
| /linux-4.4.14/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-4.4.14/Documentation/cgroups/ |
| D | hugetlb.txt | 31 hugetlb.<hugepagesize>.max_usage_in_bytes # show max "hugepagesize" hugetlb usage recorded
|
| D | memory.txt | 68 memory.max_usage_in_bytes # show max memory usage recorded
69 memory.memsw.max_usage_in_bytes # show max memory+Swap usage recorded
84 memory.kmem.max_usage_in_bytes # show max kernel memory usage recorded
89 memory.kmem.tcp.max_usage_in_bytes # show max tcp buf memory usage recorded
453 Charges recorded in swap information is not updated at removal of cgroup.
|
| /linux-4.4.14/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-4.4.14/Documentation/sound/alsa/ |
| D | Bt87x.txt | 35 recorded data is not right, try to specify the digital_rate option with
|
| D | SB-Live-mixer.txt | 148 *** inputs of the AC97 codec can be captured (recorded). ***
|
| D | HD-Audio.txt | 273 and the recorded sound contains a certain DC-offset. This is no bug
|
| /linux-4.4.14/Documentation/networking/ |
| D | scaling.txt | 241 The CPU recorded in each entry is the one which last processed the flow.
283 - The current CPU's queue head counter >= the recorded tail counter
342 The hardware queue for a flow is derived from the CPU recorded in
370 recorded. The goal of this mapping is usually to assign queues
|
| D | netdev-features.txt | 160 read the CRC recorded by the NIC on receipt of the packet.
|
| D | packet_mmap.txt | 593 - PACKET_FANOUT_QM: schedule to socket by skbs recorded queue_mapping
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats-struct.txt | 93 * xxx_count is the number of delay values recorded
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | operations.txt | 40 An operation is recorded in an fscache_operation struct:
|
| D | object.txt | 202 write ops will be transparently discarded, and nothing recorded in the
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig.debug | 126 Because zero-overhead Hardware loops are not recorded in the trace buffer,
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | nilfs2.txt | 214 The organization of the blocks is recorded in the summary information
|
| D | autofs4-mount-control.txt | 126 autofs maps. They are recorded at mount request time and an operation
|
| D | xfs-delayed-logging-design.txt | 22 new change to the object is recorded with a *new copy* of all the existing
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 317 taken in the kernel is recorded whether it hit or miss.
580 it recorded and give a rough estimate of how long each iteration took.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-raid.txt | 188 discrepancies found are recorded in
|
| /linux-4.4.14/Documentation/ |
| D | md.txt | 340 recorded in the metadata.
460 recorded to disk safely) bad blocks.
|
| D | HOWTO | 379 already discussed in detail are only recorded at the mailing list
|
| /linux-4.4.14/Documentation/scsi/ |
| D | st.txt | 379 MTEOM Space to end of recorded data.
532 end of recorded data or end of tape. GMT_EOT means end of tape.
|
| /linux-4.4.14/drivers/mtd/nand/ |
| D | Kconfig | 267 are detected by Linux, they will not be recorded in the BBT, which
|
| /linux-4.4.14/Documentation/security/ |
| D | credentials.txt | 240 recorded in the file struct created. This allows operations using that file
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 11 The timestamp is always recorded internally, and exported
13 be included, not that the timestamp is recorded.
|
| /linux-4.4.14/Documentation/power/ |
| D | pci.txt | 212 and event sources is recorded in the system's ACPI BIOS from where it can be
249 recorded in one of the root port's configuration registers from where it may be
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 709 Also recorded is the total bytes read and bytes written to the server for
|