| /linux-6.12.1/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | memory.json | 6 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
12 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
48 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was group pu…
65 … "BriefDescription": "Pump prediction correct. Counts across all types of pumps for a demand load",
71 "BriefDescription": "Pump misprediction. Counts across all types of pumps for a demand load",
72 "PublicDescription": "Pump Mis prediction Counts across all types of pumpsfor a demand load"
78 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was system p…
113 …"BriefDescription": "Initial and Final Pump Scope and data sourced across this scope was group pum…
185 …"BriefDescription": "Pump prediction correct. Counts across all types of pumps for all data types …
186 …"PublicDescription": "Pump prediction correct. Counts across all types of pumpsfor all data types …
[all …]
|
| /linux-6.12.1/tools/testing/selftests/powerpc/dexcr/ |
| D | dexcr_test.c | 24 "setting aspect across exec not applied"); in dexcr_prctl_onexec_test_child()
27 "setting aspect across exec not inherited"); in dexcr_prctl_onexec_test_child()
29 FAIL_IF_EXIT_MSG(!(aspect & dexcr), "setting aspect across exec did not take effect"); in dexcr_prctl_onexec_test_child()
32 "clearing aspect across exec not applied"); in dexcr_prctl_onexec_test_child()
35 "clearing aspect across exec not inherited"); in dexcr_prctl_onexec_test_child()
37 FAIL_IF_EXIT_MSG(aspect & dexcr, "clearing aspect across exec did not take effect"); in dexcr_prctl_onexec_test_child()
126 /* Verify the onexec value is applied across exec */ in dexcr_prctl_aspect_test()
136 "setting aspect on exec not copied across fork"); in dexcr_prctl_aspect_test()
158 "clearing aspect on exec not copied across fork"); in dexcr_prctl_aspect_test()
191 * Some tests require checking what happens across exec, so we may be in main()
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-interconnect.json | 359 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If…
706 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t…
864 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
873 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
883 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
893 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
903 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
913 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
923 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
933 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | uncore-interconnect.json | 7 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u…
17 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u…
570 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If…
686 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t…
844 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
853 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
863 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
873 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
883 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
893 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-interconnect.json | 349 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If…
425 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t…
523 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
532 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
542 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
552 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
562 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
572 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
582 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
592 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break…
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | uncore-interconnect.json | 7 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u…
17 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u…
570 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If…
686 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t…
843 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
852 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
862 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
872 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
882 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
892 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas…
[all …]
|
| /linux-6.12.1/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-dds | 18 obtain the desired value in Hz. If shared across all frequency
20 if shared across all channels.
48 the desired value in rad. If shared across all phase registers
50 shared across all channels.
|
| /linux-6.12.1/tools/arch/powerpc/include/asm/ |
| D | barrier.h | 18 * mb() prevents loads and stores being reordered across this point.
19 * rmb() prevents loads being reordered across this point.
20 * wmb() prevents stores being reordered across this point.
|
| /linux-6.12.1/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 71 The unwinding process varies across architectures, their respective procedure
132 4.3 Unwinding across interrupts and exceptions
149 (or where it is never reliable) must reject unwinding across exception
150 boundaries. Note that it may be reliable to unwind across certain
151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions
155 have no such cases) should attempt to unwind across exception boundaries, as
307 the case must reject unwinding across exception boundaries unless they can
|
| /linux-6.12.1/arch/arm/mach-omap2/ |
| D | powerdomain-common.c | 25 /* OMAP3 and OMAP4 Memory Onstate Masks (common across all power domains) */
32 /* OMAP3 and OMAP4 Memory Retstate Masks (common across all power domains) */
46 /* Common Internal functions used across OMAP rev's*/
|
| /linux-6.12.1/Documentation/userspace-api/ |
| D | no_new_privs.rst | 23 execution environment in a manner that persists across execve. Any task
24 can set ``no_new_privs``. Once the bit is set, it is inherited across fork,
47 - Filters installed for the seccomp mode 2 sandbox persist across
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | ltc2990.rst | 55 curr1_input Current in mA across V1-V2 assuming a 1mOhm sense resistor
56 curr2_input Current in mA across V3-V4 assuming a 1mOhm sense resistor
59 The "curr*_input" measurements actually report the voltage drop across the
|
| /linux-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | switch.rst | 6 arbitrary mapping of fixed-size regions of I/O across a fixed set of
22 is created it is spread across multiple members. The details of the
38 robin algorithm to send I/O across all paths and let the storage array
73 The number of paths across which to distribute the I/O.
|
| /linux-6.12.1/Documentation/filesystems/nfs/ |
| D | pnfs.rst | 20 We reference the header for the inode pointing to it, across each
34 nfs4_deviceid_cache). The cache itself is referenced across each
35 mount. The entries (struct nfs4_deviceid) themselves are held across
|
| /linux-6.12.1/net/l2tp/ |
| D | Kconfig | 16 L2TP facilitates the tunneling of packets across an
59 mechanism for tunneling Layer 2 (L2) "circuits" across a
99 across an IP network [RFC3931].
|
| /linux-6.12.1/tools/include/uapi/asm-generic/ |
| D | mman-common.h | 51 /* common parameters: try to keep these consistent across architectures */
54 #define MADV_DONTFORK 10 /* don't inherit across fork */
55 #define MADV_DOFORK 11 /* do inherit across fork */
|
| /linux-6.12.1/arch/powerpc/include/asm/ |
| D | barrier.h | 22 * mb() prevents loads and stores being reordered across this point.
23 * rmb() prevents loads being reordered across this point.
24 * wmb() prevents stores being reordered across this point.
|
| /linux-6.12.1/include/uapi/asm-generic/ |
| D | mman-common.h | 51 /* common parameters: try to keep these consistent across architectures */
54 #define MADV_DONTFORK 10 /* don't inherit across fork */
55 #define MADV_DOFORK 11 /* do inherit across fork */
|
| /linux-6.12.1/Documentation/staging/ |
| D | rpmsg.rst | 73 sends a message across to the remote processor from the given endpoint.
93 sends a message across to the remote processor from a given endpoint,
119 sends a message across to the remote processor, using the src and dst
142 sends a message across to the remote processor from a given endpoint.
160 sends a message across to the remote processor from a given endpoint,
182 sends a message across to the remote processor, using source and
|
| /linux-6.12.1/Documentation/trace/ |
| D | hwlat_detector.rst | 76 - tracing_cpumask - the CPUs to move the hwlat thread across
81 By default, one hwlat detector's kernel thread will migrate across each CPU
87 - round-robin: migrate across each CPU specified in cpumask [default]
|
| /linux-6.12.1/Documentation/networking/devlink/ |
| D | devlink-params.rst | 13 across multiple drivers. Each driver is also free to add their own
70 create. Value is the same across all physical functions (PFs) in the
75 device to initialize. Value is the same across all physical functions
|
| /linux-6.12.1/arch/arm/include/asm/ |
| D | fiq.h | 9 * NOTE: The FIQ mode registers are not magically preserved across
12 * Drivers which require these registers to be preserved across power
|
| /linux-6.12.1/arch/mips/include/uapi/asm/ |
| D | mman.h | 78 /* common parameters: try to keep these consistent across architectures */
81 #define MADV_DONTFORK 10 /* don't inherit across fork */
82 #define MADV_DOFORK 11 /* do inherit across fork */
|
| /linux-6.12.1/arch/xtensa/include/uapi/asm/ |
| D | mman.h | 87 /* common parameters: try to keep these consistent across architectures */
90 #define MADV_DONTFORK 10 /* don't inherit across fork */
91 #define MADV_DOFORK 11 /* do inherit across fork */
|
| /linux-6.12.1/arch/arm/mach-omap1/ |
| D | reset.c | 19 /* Standardized reset source bits (across all OMAP SoCs) */
44 * format is standardized across OMAPs for use by the OMAP watchdog.
|