Lines Matching refs:inbound
90 state value into two parts (the "cluster" state and "inbound" state) and
222 as seen by a CPU tearing the cluster down. The "inbound side" is the
237 "inbound" state: The state of the cluster on the inbound side.
266 Transitions ===##> can only be made by the inbound CPU, and only
267 involve changes to the "inbound" state, except where there is no
280 The parallelism of the inbound and outbound CPUs is observed by
296 <cluster state>/<inbound state> (<transitioner>)
299 can occur; either the inbound or the outbound side.
304 CLUSTER_DOWN/INBOUND_COMING_UP (inbound)
317 In this state, an inbound CPU sets up the cluster, including
327 CLUSTER_UP/INBOUND_COMING_UP (inbound)
345 CLUSTER_UP/INBOUND_NOT_COMING_UP (inbound)
380 should check the inbound cluster state for asynchronous
393 CLUSTER_GOING_DOWN/INBOUND_COMING_UP (inbound)
417 in the CLUSTER_DOWN state; the inbound CPU will
449 The CPU which performs cluster setup on the inbound side is commonly
486 arch/arm/common/mcpm_head.S (low-level inbound CPU operations) and