Searched refs:bringup (Results 1 – 6 of 6) sorted by relevance
75 bool bringup; member101 static inline void cpuhp_lock_acquire(bool bringup) in cpuhp_lock_acquire() argument103 lock_map_acquire(bringup ? &cpuhp_state_up_map : &cpuhp_state_down_map); in cpuhp_lock_acquire()106 static inline void cpuhp_lock_release(bool bringup) in cpuhp_lock_release() argument108 lock_map_release(bringup ? &cpuhp_state_up_map : &cpuhp_state_down_map); in cpuhp_lock_release()112 static inline void cpuhp_lock_acquire(bool bringup) { } in cpuhp_lock_acquire() argument113 static inline void cpuhp_lock_release(bool bringup) { } in cpuhp_lock_release() argument152 static bool cpuhp_step_empty(bool bringup, struct cpuhp_step *step) in cpuhp_step_empty() argument154 return bringup ? !step->startup.single : !step->teardown.single; in cpuhp_step_empty()170 bool bringup, struct hlist_node *node, in cpuhp_invoke_callback() argument[all …]
25 of access initially with the bringup mode set on the
167 * Crashes in early boot, especially around CPU bringup. Bugs
859 configuration and system bringup easier. Configure the kernel with860 CONFIG_SECURITY_SMACK_BRINGUP to enable these features. When bringup866 Another feature of bringup mode is the "unconfined" option. Writing
1023 [SMP] Enable/disable parallel bringup of secondary CPUs7215 'core_id % n'. This is setup before SMP bringup and7216 used during SMP bringup before it knows the full
3250 neighbor advertisements on interface bringup. This setting should be