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

Searched full:across (Results 1 – 25 of 2321) sorted by relevance

/openbmc/linux/tools/perf/pmu-events/arch/powerpc/power8/
H A 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 …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	320 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If… 622 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t… 764 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 772 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 781 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 790 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 799 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 808 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 817 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 826 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… [all …]
/openbmc/qemu/tests/qemu-iotests/
H A D	171.out	`23 write across image boundary 39 read across image boundary 62 write zeroes across image boundary 84 discard across image boundary 115 write across image boundary 131 read across image boundary 154 write zeroes across image boundary 178 discard across image boundary 211 write across image boundary 227 read across image boundary [all …]`
H A D	171	`83 echo "write across image boundary" 103 echo "read across image boundary" 128 echo "write zeroes across image boundary" 147 echo "discard across image boundary"`
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-interconnect.json	311 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If… 379 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t… 467 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 475 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 484 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 493 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 502 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 511 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 520 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… 529 …'data' bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-interconnect.json	6 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u… 15 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u… 511 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If… 615 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t… 756 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 764 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 773 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 782 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 791 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 800 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-interconnect.json	6 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u… 15 …across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made u… 511 …ounts the number of CTO (cluster trigger outs) events that were asserted across the two slots. If… 615 …at an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into t… 757 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 765 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 774 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 783 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 792 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… 801 …les that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypas… [all …]
/openbmc/linux/tools/arch/powerpc/include/asm/
H A 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.`
/openbmc/linux/drivers/staging/iio/Documentation/
H A 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.`
/openbmc/qemu/docs/system/devices/
H A D	cxl.rst	60 persistent memory. The CXL topology may support interleaving across a 88 decisions about how to configure interleave across available CXL 109 may be a mapping to a single Root Port (RP) or across a set of 167 \| \| \| \| memory accesses across HB0/HB1 \| \| \| \| 210 particular interleave setup across the CXL Host Bridges (HB) 213 across HB0 and HB1. 217 a single port or interleave them across multiple ports. 223 CFMW0 to be interleaved across RP0 and RP1, providing 2 way 228 across for example CXL Type3 0 and CXL Type3 2). 229 HDM4 is used to enable system wide 4 way interleave across all [all …]
/openbmc/phosphor-led-manager/manager/
H A D	config-validator.cpp	`16 // Priority for a particular LED needs to stay SAME across all groups 52 /** @brief Validate the Priority of an LED is same across ALL groups 76 "Priority of the LED is not same across groups. Old Priority = " + in validatePriority() 103 // priorities across groups need to match. in validateConfigV1GroupForLedPriority()`
/openbmc/linux/arch/arm/mach-omap2/
H A 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*/`
/openbmc/linux/Documentation/livepatch/
H A 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
/openbmc/linux/Documentation/userspace-api/
H A 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
/openbmc/qemu/include/crypto/
H A D	hmac.h	`79 * Computes the hmac across all the memory regions 112 * Computes the hmac across all the memory region 144 * Computes the hmac across all the memory regions 168 * Computes the hmac across all the memory region`
H A D	hash.h	`76 * Computes the hash across all the memory regions 108 * Computes the hash across all the memory region 139 * Computes the hash across all the memory regions 282 * Computes the hash across all the memory region 305 * Computes the hash across all the memory regions 328 * Computes the hash across all the memory region`
/openbmc/linux/Documentation/hwmon/
H A 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`
/openbmc/linux/Documentation/filesystems/nfs/
H A 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`
/openbmc/qemu/docs/system/
H A D	cpu-models-mips.rst.inc	`14 across all desired hosts. 46 across all desired hosts. 90 across all desired hosts.`
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A 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.`
/openbmc/linux/net/l2tp/
H A 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].`
/openbmc/linux/tools/include/uapi/asm-generic/
H A 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 */`
/openbmc/linux/arch/powerpc/include/asm/
H A 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.`
/openbmc/qemu/linux-headers/asm-generic/
H A 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 */`
/openbmc/linux/include/uapi/asm-generic/
H A 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 */`

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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type