Lines Matching +full:0487 +full:a
32 * The safe value of a CPUID feature field is dependent on the implications
39 * a field when EXACT is specified, failing which, the safe value specified
44 FTR_EXACT, /* Use a predefined safe value */
80 * A @mask field set to full-1 indicates that the corresponding field
81 * in @val is a valid override.
83 * A @mask field set to full-0 with the corresponding @val field set
86 * A @mask field set to full-0 with the corresponding @val field set
125 * 1) Scope of Detection : The system detects a given capability by
127 * value of a field in CPU ID feature register or checking the cpu
128 * model. The capability provides a call back ( @matches() ) to
132 * a) SCOPE_LOCAL_CPU: check all the CPUs and "detect" if at least one
140 * capability relies on a field in one of the CPU ID feature
152 * 2) Finalise the state : The kernel should finalise the state of a
160 * changes to the state of a capability once it finalises the capability
162 * safely. A CPU brought up after a capability is "finalised" is
168 * a) Boot CPU scope capabilities - Finalised by primary boot CPU via
170 * b) Everything except (a) - Run via setup_system_capabilities().
172 * 3) Verification: When a CPU is brought online (e.g, by user or by the
184 * a) SCOPE_BOOT_CPU : All CPUs are verified against the capability
190 * If there is a conflict, the kernel takes an action, based on the
191 * severity (e.g, a CPU could be prevented from booting or cause a
204 * a) Action is triggered on all online CPUs, after the capability is
212 * 5) Conflicts: Based on the state of the capability on a late CPU vs.
218 * | a | y | n |
225 * ARM64_CPUCAP_OPTIONAL_FOR_LATE_CPU - Case(a) is allowed
228 * Case (a) is not permitted for a capability that the system requires
232 * Case (b) is not permitted for a capability that must be enabled
237 * In some non-typical cases either both (a) and (b), or neither,
241 * In case of a conflict, the CPU is prevented from booting. If the
243 * then a kernel panic is triggered.
270 * Is it permitted for a late CPU to have this capability when system
274 /* Is it safe for a late CPU to miss this capability when system has it */
276 /* Panic when a conflict is detected */
283 * require the workaround. However, it is not safe if a "late" CPU
284 * requires a workaround and the system hasn't enabled it already.
289 * CPU feature detected at boot time based on system-wide value of a
290 * feature. It is safe for a late CPU to have this feature even though
299 * All possible conflicts for a late CPU are ignored.
300 * NOTE: this means that a late CPU with the feature will *not* cause the
309 * CPU feature detected at boot time, on one or more CPUs. A late CPU
311 * It is Ok for a late CPU to miss the feature.
320 * case of a conflict, a kernel panic is triggered.
326 * CPU feature used early in the boot based on the boot CPU. It is safe for a
380 * However, if a cpu_enable() method is associated
457 * Test for a capability with a runtime check.
471 * Test for a capability without a runtime check.
474 * After boot capabilities are finalized, this is patched to avoid a runtime
477 * @num must be a compile-time constant.
488 * Test for a capability without a runtime check.
491 * After system capabilities are finalized, this is patched to avoid a runtime
494 * @num must be a compile-time constant.
530 * not follow the standard ID scheme. See ARM DDI 0487E.a page D13-2825,
883 * A future PE could use a value unknown to the kernel. in id_aa64mmfr0_parange_to_phys_shift()
885 * for fields in ID registers", ARM DDI 0487C.a, any new in id_aa64mmfr0_parange_to_phys_shift()
887 * As a safe limit, we return the limit supported by the kernel. in id_aa64mmfr0_parange_to_phys_shift()
927 /* Get a cpu that supports the Activity Monitors Unit (AMU) */
969 * cannot be honoured due to a missing CPU feature), the early idreg in arm64_apply_feature_override()