| /openbmc/linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/skylake/ |
| H A D | virtual-memory.json | 6 … data loads that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
31 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
39 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
47 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
55 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
71 …data stores that caused a page walk of any page size (4K/2M/4M/1G). This implies it missed in all …
96 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
104 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
112 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
120 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
39 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
47 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
80 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
88 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
96 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
104 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
137 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
145 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
39 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
47 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
80 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
88 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
96 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
104 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
137 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
145 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| H A D | virtual-memory.json | 34 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
43 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
52 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
61 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
107 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
116 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
125 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
134 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
196 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
205 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
80 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
88 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
80 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
88 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | virtual-memory.json | 41 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
50 …ounts completed page walks (1G sizes) caused by demand data loads. This implies address translati…
68 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
77 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
139 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
148 …unts completed page walks (1G sizes) caused by demand data stores. This implies address translati…
157 …s completed page walks (2M/4M sizes) caused by demand data stores. This implies address translati…
166 …unts completed page walks (4K sizes) caused by demand data stores. This implies address translati…
237 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
255 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | virtual-memory.json | 23 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
31 …ts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translati…
39 …ounts completed page walks (4K sizes) caused by demand data loads. This implies address translati…
72 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
121 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
129 …nts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the …
137 …Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the …
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | BMC.interface.yaml | 4 successfully. When we are Not Ready this implies not all services have
54 Ready implies all services started and are running successfully
57 Not ready implies not all services have started or are not
61 UpdateInProgress implies BMC is in firmware update mode.
|
| H A D | Drive.interface.yaml | 62 Ready implies all services started and are running successfully
65 Not ready implies not all services have started or are not
76 UpdateInProgress implies the Drive is in firmware update mode.
|
| /openbmc/linux/arch/xtensa/include/asm/ |
| H A D | asm-uaccess.h | 31 * <error>. This implies that the macro falls through to the next
42 * <error> label to branch to on error; implies fall-through
61 * <error>. This implies that the macro falls through to the next
72 * <error> label to branch to on error; implies fall-through
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/silvermont/ |
| H A D | virtual-memory.json | 15 …page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the a…
32 …ts when a data (D) page walk is completed or started. Since a page walk implies a TLB miss, the n…
49 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
58 …an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, the n…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | virtual-memory.json | 6 …completed page walks (all page sizes) caused by demand data loads. This implies it missed in the …
14 …ompleted page walks (all page sizes) caused by demand data stores. This implies it missed in the …
22 …ounts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the …
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | sync_bitops.h | 81 * It also implies a memory barrier.
94 * It also implies a memory barrier.
107 * It also implies a memory barrier.
|
| /openbmc/linux/tools/perf/pmu-events/arch/powerpc/power10/ |
| H A D | frontend.json | 5 …"BriefDescription": "Data TLB hit (DERAT reload) page size 2M. Implies radix translation. When MMC…
55 …"BriefDescription": "Instruction TLB hit (IERAT reload) page size 1G, which implies Radix Page Tab…
85 …"BriefDescription": "Data TLB hit (DERAT reload) page size 1G. Implies radix translation. When MMC…
|
| H A D | memory.json | 20 …"BriefDescription": "Data TLB reload (after a miss) page size 2M. Implies radix translation was us…
55 …"BriefDescription": "Data ERAT Miss (Data TLB Access) page size 1G. Implies radix translation. Whe…
110 …"BriefDescription": "Data TLB reload (after a miss) page size 1G. Implies radix translation was us…
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | counters.rst | 919 on a physical port. If this counter is increasing, it implies that the
926 size on a physical port. If this counter is increasing, it implies that
946 this counter is increasing, it implies that the network is congested and
952 this counter is increasing, it implies that the NIC is congested and
963 physical port. If this counter is increasing, it implies that the adapter
981 implies that the peer connected to the adapter has a non-standard MTU
988 increasing, it implies that the peer connected to the adapter has a
1107 interface. If this counter is increasing, it implies that the link
1116 (RS/FC). If this counter is increasing, it implies that the link between
1125 increasing, it implies that the link between the NIC and the network is
[all …]
|
| /openbmc/linux/arch/mips/include/asm/ |
| H A D | bitops.h | 139 * clear_bit() is atomic and implies release semantics before the memory
175 * This operation is atomic and implies acquire ordering semantics
205 * It also implies a memory barrier.
220 * It also implies a memory barrier.
257 * It also implies a memory barrier.
292 * __clear_bit() is non-atomic and implies release semantics before the memory
|
| /openbmc/linux/arch/arm/common/ |
| H A D | mcpm_head.S | 103 bl vlock_trylock @ implies DMB
118 @ Control dependency implies strb not observable before previous ldrb.
165 bl vlock_unlock @ implies DMB
|
| /openbmc/linux/arch/powerpc/perf/ |
| H A D | hv-gpci.c | 152 * ret value as H_AUTHORITY implies that partition is not permitted to retrieve in systeminfo_gpci_request()
206 * starting_index value implies the starting hardware in processor_bus_topology_show()
220 * implies that buffer can't accommodate all information, and a partial buffer in processor_bus_topology_show()
274 * starting_index value implies the starting hardware in processor_config_show()
288 * implies that buffer can't accommodate all information, and a partial buffer in processor_config_show()
356 * implies that buffer can't accommodate all information, and a partial buffer in affinity_domain_via_virtual_processor_show()
426 * implies that buffer can't accommodate all information, and a partial buffer in affinity_domain_via_domain_show()
541 * ret value as 'H_PARAMETER' implies that the current buffer size in affinity_domain_via_partition_show()
598 * ret value as H_AUTHORITY implies that partition is not permitted to retrieve in affinity_domain_via_partition_show()
816 * ret value as H_AUTHORITY implies that partition is not permitted to retrieve in h_gpci_event_init()
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinctrl-vt8500.txt | 26 listed. In other words, a subnode that lists only a mux function implies no
28 a pull parameter implies no information about the mux function.
|
| /openbmc/u-boot/arch/nios2/include/asm/bitops/ |
| H A D | atomic.h | 125 * It also implies a memory barrier.
149 * It also implies a memory barrier.
172 * It also implies a memory barrier.
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pmc.txt | 8 whose PMC is compatible, and implies deep-sleep capability.
12 whose PMC is compatible, and implies deep-sleep capability.
|