each (full) in projects: openbmc - OpenGrok search results

Searched full:each (Results 1 – 25 of 6797) sorted by relevance

/openbmc/linux/tools/perf/pmu-events/arch/x86/rocketlake/
H A D	floating-point.json	11 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 35 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 38 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 46 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelake/
H A D	floating-point.json	11 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 35 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 38 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 46 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A D	floating-point.json	11 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 35 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 38 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 46 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	floating-point.json	11 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 35 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 38 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 46 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	floating-point.json	6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 46 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 51 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 54 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	floating-point.json	47 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 50 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 55 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 58 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 63 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 66 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 71 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 74 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 79 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 82 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/
H A D	cache.json	114 …"PublicDescription": "L2 cache write streaming mode. This event counts for each cycle where the co… 117 …"BriefDescription": "L2 cache write streaming mode. This event counts for each cycle where the cor… 120 …ion": "L1 data cache entering write streaming mode. This event counts for each entry into write st… 123 …ion": "L1 data cache entering write streaming mode. This event counts for each entry into write st… 126 …"PublicDescription": "L1 data cache write streaming mode. This event counts for each cycle where t… 129 …"BriefDescription": "L1 data cache write streaming mode. This event counts for each cycle where th… 132 …"PublicDescription": "L3 cache write streaming mode. This event counts for each cycle where the co… 135 …"BriefDescription": "L3 cache write streaming mode. This event counts for each cycle where the cor… 138 …"PublicDescription": "Last level cache write streaming mode. This event counts for each cycle wher… 141 …"BriefDescription": "Last level cache write streaming mode. This event counts for each cycle where… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	floating-point.json	6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 46 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 51 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 54 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/alderlake/
H A D	floating-point.json	53 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 56 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 62 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 65 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 71 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 74 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 80 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 83 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 89 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 92 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/meteorlake/
H A D	floating-point.json	53 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 56 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 62 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 65 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 71 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 74 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 80 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 83 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 89 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 92 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/
H A D	trace.json	4 …"PublicDescription": "This event is generated each time the current write pointer is wrapped to th… 8 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 12 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 16 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 20 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 24 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 28 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 32 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 36 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
H A D	cache.json	123 …"PublicDescription": "Level 2 cache write streaming mode. This event counts for each cycle where t… 126 …"BriefDescription": "Level 2 cache write streaming mode. This event counts for each cycle where th… 129 …: "Level 1 data cache entering write streaming mode.This event counts for each entry into write-st… 132 …: "Level 1 data cache entering write streaming mode.This event counts for each entry into write-st… 135 …"PublicDescription": "Level 1 data cache write streaming mode.This event counts for each cycle whe… 138 …"BriefDescription": "Level 1 data cache write streaming mode.This event counts for each cycle wher… 141 …"PublicDescription": "Level 3 cache write streaming mode.This event counts for each cycle where th… 144 …"BriefDescription": "Level 3 cache write streaming mode.This event counts for each cycle where the… 171 …This event counts on each access to the IPA cache. +//0 If a single pagewalk needs to make multipl… 174 …This event counts on each access to the IPA cache. +//0 If a single pagewalk needs to make multipl… [all …]
/openbmc/u-boot/drivers/pinctrl/renesas/
H A D	Kconfig	16 the GPIO definitions and pin control functions for each available 26 the GPIO definitions and pin control functions for each available 36 the GPIO definitions and pin control functions for each available 46 the GPIO definitions and pin control functions for each available 56 the GPIO definitions and pin control functions for each available 66 the GPIO definitions and pin control functions for each available 76 the GPIO definitions and pin control functions for each available 86 the GPIO definitions and pin control functions for each available 96 the GPIO definitions and pin control functions for each available 106 the GPIO definitions and pin control functions for each available
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 11 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 11 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwell/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 11 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 19 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 27 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/openbmc/linux/Documentation/filesystems/nfs/
H A D	pnfs.rst	6 reference multiple devices, each of which can reference multiple data servers. 7 Each data server can be referenced by multiple devices. Each device 17 Each nfs_inode may hold a pointer to a cache of these layout 20 We reference the header for the inode pointing to it, across each 22 LAYOUTCOMMIT), and for each lseg held within. 24 Each header is also (when non-empty) put on a list associated with 34 nfs4_deviceid_cache). The cache itself is referenced across each 36 the lifetime of each lseg referencing them. 66 layout types: "files", "objects", "blocks", and "flexfiles". For each
/openbmc/linux/Documentation/hwmon/
H A D	ibmpowernv.rst	`18 'hwmon' populates the 'sysfs' tree having attribute files, each for a given 21 All the nodes in the DT appear under "/ibm,opal/sensors" and each valid node in 45 each OCC. Using this attribute each OCC can be asked to 58 each OCC. Using this attribute each OCC can be asked to 69 each OCC. Using this attribute each OCC can be asked to 80 each OCC. Using this attribute each OCC can be asked to`
/openbmc/linux/tools/perf/pmu-events/arch/x86/skylake/
H A D	floating-point.json	6 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 14 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 22 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 35 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 38 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 46 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 54 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 62 …instructions retired; some instructions will count twice as noted below. Each count represents 1 …
/openbmc/linux/lib/842/
H A D	842.h	6 /* The 842 compressed format is made up of multiple blocks, each of 12 * template operation. For normal operations, each arg is either a specific 18 * table, the static "decomp_ops" table used in decompress. For each template 19 * (table row), there are between 1 and 4 actions; each action corresponds to 20 * an arg following the template code bits. Each action is either a "data" 21 * type action, or a "index" type action, and each action results in 2, 4, or 8 22 * bytes being written to the output buffer. Each template (i.e. all actions 36 * The number of bits for each index's arg are: 8 bits for I2, 9 bits for I4, 37 * and 8 bits for I8. Since each index points to a 2, 4, or 8 byte section, 41 * each of I2, I4, and I8 that are updated for each byte written to the output [all …]
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A D	pinctrl-bindings.txt	5 controllers. Each pin controller must be represented as a node in device tree, 9 designated client devices. Again, each client device must be represented as a 16 device is inactive. Hence, each client device can define a set of named 35 For each client device individually, every pin state is assigned an integer 36 ID. These numbers start at 0, and are contiguous. For each state ID, a unique 37 property exists to define the pin configuration. Each state may also be 41 Each client device's own binding determines the set of states that must be 47 pinctrl-0: List of phandles, each pointing at a pin configuration 52 from multiple nodes for a single pin controller, each 65 pinctrl-1: List of phandles, each pointing at a pin configuration [all …]
/openbmc/linux/Documentation/ABI/testing/
H A D	debugfs-scmi-raw	11 Each write to the entry causes one command request to be built 13 (receiving an EOF at each message boundary). 29 Each write to the entry causes one command request to be built 31 (receiving an EOF at each message boundary). 41 Each read gives back one message at time (receiving an EOF at 42 each message boundary). 52 Each read gives back one message at time (receiving an EOF at 53 each message boundary). 80 Each write to the entry causes one command request to be built 82 (receiving an EOF at each message boundary). [all …]
/openbmc/u-boot/doc/device-tree-bindings/gpio/
H A D	nvidia,tegra186-gpio.txt	26 address space, each of which access the same underlying state. See the hardware 31 implemented by the SoC. Each GPIO is assigned to a port, and a port may control 32 a number of GPIOs. Thus, each GPIO is named according to an alphabetical port 36 The number of ports implemented by each GPIO controller varies. The number of 37 implemented GPIOs within each port varies. GPIO registers within a controller 48 Each GPIO controller can generate a number of interrupt signals. Each signal 54 Each GPIO controller in fact generates multiple interrupts signals for each set 55 of ports. Each GPIO may be configured to feed into a specific one of the 56 interrupt signals generated by a set-of-ports. The intent is for each generated 57 signal to be routed to a different CPU, thus allowing different CPUs to each [all …]
/openbmc/u-boot/doc/device-tree-bindings/gpu/
H A D	nvidia,tegra20-host1x.txt	14 - resets: Must contain an entry for each entry in reset-names. 19 The host1x top-level node defines a number of children, each representing one 30 - resets: Must contain an entry for each entry in reset-names. 43 - resets: Must contain an entry for each entry in reset-names. 56 - resets: Must contain an entry for each entry in reset-names. 69 - resets: Must contain an entry for each entry in reset-names. 82 - resets: Must contain an entry for each entry in reset-names. 92 - clocks: Must contain an entry for each entry in clock-names. 99 - resets: Must contain an entry for each entry in reset-names. 111 - clocks: Must contain an entry for each entry in clock-names. [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A D	floating-point.json	6 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 13 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 20 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 27 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 34 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 41 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 48 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 55 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 62 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 69 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may …

12 3 4 5 6 7 8 9 10 >>...272

Project(s)

Full Search
Definition
Symbol
File Path
History
Type