| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
| D | other.json | 9 …"PublicDescription": "This event counts every cycle that no operation was committed because the ol…
12 …"BriefDescription": "This event counts every cycle that no operation was committed because the old…
15 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
18 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
21 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
24 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
27 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
30 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
33 …"PublicDescription": "This event counts every cycle that no instruction was committed because the …
36 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| D | pipeline.json | 9 …": "No operation issued due to the frontend, cache miss.This event counts every cycle the DPU IQ i…
12 …": "No operation issued due to the frontend, cache miss.This event counts every cycle the DPU IQ i…
15 …on": "No operation issued due to the frontend, TLB miss.This event counts every cycle the DPU IQ i…
18 …on": "No operation issued due to the frontend, TLB miss.This event counts every cycle the DPU IQ i…
21 … operation issued due to the frontend, pre-decode error.This event counts every cycle the DPU IQ i…
24 … operation issued due to the frontend, pre-decode error.This event counts every cycle the DPU IQ i…
27 …ion": "No operation issued due to the backend interlock.This event counts every cycle that issue i…
30 …ion": "No operation issued due to the backend interlock.This event counts every cycle that issue i…
33 …"No operation issued due to the backend, interlock, AGU.This event counts every cycle that issue i…
36 …"No operation issued due to the backend, interlock, AGU.This event counts every cycle that issue i…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/ |
| D | pipeline.json | 21 …: "No operation issued due to the frontend, cache miss. This event counts every cycle that the Dat…
24 …: "No operation issued due to the frontend, cache miss. This event counts every cycle that the Dat…
27 …n": "No operation issued due to the frontend, TLB miss. This event counts every cycle that the DPU…
30 …n": "No operation issued due to the frontend, TLB miss. This event counts every cycle that the DPU…
39 …on": "No operation issued due to the backend interlock. This event counts every cycle where the is…
42 …on": "No operation issued due to the backend interlock. This event counts every cycle where the is…
45 …operation issued due to the backend, address interlock. This event counts every cycle where the is…
48 …operation issued due to the backend, address interlock. This event counts every cycle where the is…
51 …ackend, interlock, or the Vector Processing Unit (VPU). This event counts every cycle where there …
54 …ackend, interlock, or the Vector Processing Unit (VPU). This event counts every cycle where there …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | uncore-memory.json | 3 …"BriefDescription": "Counts every CAS read command sent from the Memory Controller 0 to DRAM (sum …
7 …"PublicDescription": "Counts every CAS read command sent from the Memory Controller 0 to DRAM (sum…
12 "BriefDescription": "Counts every read and write request entering the Memory Controller 0.",
16 …"PublicDescription": "Counts every read and write request entering the Memory Controller 0 (sum of…
21 …"BriefDescription": "Counts every CAS write command sent from the Memory Controller 0 to DRAM (sum…
25 …"PublicDescription": "Counts every CAS write command sent from the Memory Controller 0 to DRAM (su…
30 …"BriefDescription": "Counts every CAS read command sent from the Memory Controller 1 to DRAM (sum …
34 …"PublicDescription": "Counts every CAS read command sent from the Memory Controller 1 to DRAM (sum…
39 "BriefDescription": "Counts every read and write request entering the Memory Controller 1.",
43 …"PublicDescription": "Counts every read and write request entering the Memory Controller 1 (sum of…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | pipeline.json | 265 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
279 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
294 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
300 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
307 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
314 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
321 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
328 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
335 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
350 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| D | pipeline.json | 265 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
279 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
294 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
300 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
307 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
314 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
321 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
328 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
335 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
350 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | uncore-memory.json | 3 …"BriefDescription": "Counts every read (RdCAS) issued by the Memory Controller to DRAM (sum of all…
11 …"BriefDescription": "Counts every 64B read and write request entering the Memory Controller to DRA…
19 …"BriefDescription": "Counts every write (WrCAS) issued by the Memory Controller to DRAM (sum of al…
27 …"BriefDescription": "Counts every read (RdCAS) issued by the Memory Controller to DRAM (sum of all…
35 …"BriefDescription": "Counts every 64B read and write request entering the Memory Controller to DRA…
43 …"BriefDescription": "Counts every write (WrCAS) issued by the Memory Controller to DRAM (sum of al…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlaken/ |
| D | pipeline.json | 347 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
361 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
368 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
375 …"BriefDescription": "Counts the total number of issue slots every cycle that were not consumed by …
381 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
388 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
395 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
402 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
409 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
416 …"BriefDescription": "Counts the number of issue slots every cycle that were not consumed by the ba…
[all …]
|
| D | uncore-memory.json | 3 …"BriefDescription": "Counts every 64B read request entering the Memory Controller 0 to DRAM (sum …
7 …"PublicDescription": "Counts every 64B read request entering the Memory Controller 0 to DRAM (sum …
12 …"BriefDescription": "Counts every 64B write request entering the Memory Controller 0 to DRAM (sum …
20 …"BriefDescription": "Counts every 64B read request entering the Memory Controller 1 to DRAM (sum o…
24 …"PublicDescription": "Counts every 64B read entering the Memory Controller 1 to DRAM (sum of all c…
29 …"BriefDescription": "Counts every 64B write request entering the Memory Controller 1 to DRAM (sum …
|
| /kernel/linux/linux-5.10/drivers/thunderbolt/ |
| D | nhi_regs.h | 40 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT)
49 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT)
59 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT)
67 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT)
80 * Every bitfield contains one bit for every hop (REG_HOP_COUNT). Registers are
89 * Both bitfields contains one bit for every hop (REG_HOP_COUNT). To
|
| /kernel/linux/linux-6.6/drivers/thunderbolt/ |
| D | nhi_regs.h | 40 * 16 bytes per entry, one entry for every hop (REG_CAPS)
49 * 16 bytes per entry, one entry for every hop (REG_CAPS)
59 * 32 bytes per entry, one entry for every hop (REG_CAPS)
67 * 32 bytes per entry, one entry for every hop (REG_CAPS)
80 * Every bitfield contains one bit for every hop (REG_CAPS).
90 * Both bitfields contains one bit for every hop (REG_CAPS). To
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | frontswap.rst | 138 If CONFIG_FRONTSWAP is disabled, every frontswap hook compiles into
142 every swap page read or written. If CONFIG_FRONTSWAP is enabled
143 AND a frontswap backend registers AND the backend fails every "store"
145 CPU overhead is still negligible -- and since every frontswap fail
151 registers, one bit is allocated for every swap page for every swap
154 for every swap page for every swap device that is swapon'd. (Hugh
186 page, it could accept every ninth page, or it might accept every
201 So every time the frontswap backend accepts a page, a swap device read
249 implemented as a "shadow" to every swapon'd device with the potential
250 capability of holding every page that the swap device might have held
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | uncore-memory.json | 3 …"BriefDescription": "Counts every 64B read request entering the Memory Controller 0 to DRAM (sum …
7 …"PublicDescription": "Counts every 64B read request entering the Memory Controller 0 to DRAM (sum …
12 …"BriefDescription": "Counts every 64B write request entering the Memory Controller 0 to DRAM (sum …
20 …"BriefDescription": "Counts every 64B read request entering the Memory Controller 1 to DRAM (sum o…
24 …"PublicDescription": "Counts every 64B read entering the Memory Controller 1 to DRAM (sum of all c…
29 …"BriefDescription": "Counts every 64B write request entering the Memory Controller 1 to DRAM (sum …
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/gt/ |
| D | intel_gt_clock_utils.c | 80 * increment only every few clock cycle). in gen11_read_clock_frequency()
102 * increment only every few clock cycle). in gen9_read_clock_frequency()
118 * rolling over every 1.5 hours). in gen6_read_clock_frequency()
126 * 63:32 increments every 1000 ns in gen5_read_clock_frequency()
135 * 63:20 increments every 1/4 ns in g4x_read_clock_frequency()
138 * -> 63:32 increments every 1024 ns in g4x_read_clock_frequency()
148 * "The value in this register increments once every 16 in gen4_read_clock_frequency()
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/octeon/ |
| D | cvmx-helper-board.h | 66 * This function must be modified for every new Octeon board.
69 * fact that every Octeon board receives a unique board type
84 * This function must be modified for every new Octeon board.
87 * fact that every Octeon board receives a unique board type
106 * This function must be modified for every new Octeon board.
109 * fact that every Octeon board receives a unique board type
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-helper-board.h | 66 * This function must be modifed for every new Octeon board.
69 * fact that every Octeon board receives a unique board type
84 * This function must be modifed for every new Octeon board.
87 * fact that every Octeon board receives a unique board type
106 * This function must be modifed for every new Octeon board.
109 * fact that every Octeon board receives a unique board type
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/ |
| D | kmsan.rst | 109 in the Makefile. Think of this as applying ``__no_sanitize_memory`` to every
128 KMSAN associates a metadata byte (also called shadow byte) with every byte of
146 propagated into all the operations which use that value. For every instruction
163 Every four bytes of kernel memory also have a so-called origin mapped to them.
165 value was created. Every origin is associated with either the full allocation
172 shadow. For every instruction that takes one or more values, the origin of the
188 same four-byte chunk. In this case every write to either variable updates the
215 To ease debugging, KMSAN creates a new origin for every store of an
229 For every memory access the compiler emits a call to a function that returns a
243 The compiler makes sure that for every loaded value its shadow and origin
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 6 Every rpmsg device is a communication channel with a remote
18 Every rpmsg device is a communication channel with a remote
36 Every rpmsg device is a communication channel with a remote
58 Every rpmsg device is a communication channel with a remote
82 Every rpmsg device is a communication channel with a remote
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 6 Every rpmsg device is a communication channel with a remote
18 Every rpmsg device is a communication channel with a remote
36 Every rpmsg device is a communication channel with a remote
58 Every rpmsg device is a communication channel with a remote
82 Every rpmsg device is a communication channel with a remote
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | uncore-other.json | 578 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
590 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
602 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
614 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
626 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
638 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
650 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
662 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
722 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO …
734 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO …
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-other.json | 557 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
569 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
581 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
593 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die…
605 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
617 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
629 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
641 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca…
701 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO …
713 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO …
[all …]
|
| /kernel/linux/linux-5.10/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 26 functions. Every EPC device present in the system will have an entry in
27 the *controllers* directory and every EPF driver present in the system
38 Every registered EPF driver will be listed in controllers directory. The
53 Every <EPF device> directory consists of the following entries that can be
75 Every registered EPC device will be listed in controllers directory. The
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-script-python.txt | 74 every time a system call occurs in the system. Our script will do
79 - we could enable every event under the tracing/events/syscalls
102 The options basically say to collect data for every syscall event
161 path append which every perf script script should include.
169 every event in the 'perf record' output. The handler functions take
176 generated for every script. The first, trace_unhandled(), is called
177 every time the script finds an event in the perf.data file that
206 Of course, for this script, we're not interested in printing every
234 store that information; every time the sys_enter() handler is called,
421 the event types in the trace file; it simply prints every available
[all …]
|
| D | perf-script-perl.txt | 27 the event types in the trace file; it simply prints every available
91 to every event as arguments but are available as library functions.
107 The above provides the basics needed to directly access every field of
108 every event in a trace, which covers 90% of what you need to know to
114 Every perf script Perl script should start by setting up a Perl module
129 Aside from the event handler functions discussed above, every script
196 $context variable passed into every event handler as the second
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | perf-script-perl.txt | 27 the event types in the trace file; it simply prints every available
91 to every event as arguments but are available as library functions.
107 The above provides the basics needed to directly access every field of
108 every event in a trace, which covers 90% of what you need to know to
114 Every perf script Perl script should start by setting up a Perl module
129 Aside from the event handler functions discussed above, every script
196 $context variable passed into every event handler as the second
|