Searched refs:cpu_idle (Results 1 – 7 of 7) sorted by relevance
33 你的cpu_idle程序需要遵守以下规则：40 3. 当cpu_idle发现（need_resched() == 'true'），它应该调用schedule()。否则
18 EXPORT_TRACEPOINT_SYMBOL_GPL(cpu_idle);
24 Your cpu_idle routines need to obey the following rules:34 3. When cpu_idle finds (need_resched() == 'true'), it should call
28 cpu_idle "state=%lu cpu_id=%lu"
1222 <idle>-0 [002] .N.1 21169.031484: rcu_idle_exit <-cpu_idle1514 => cpu_idle2160 <idle>-0 3.N.1 11us : rcu_idle_exit <-cpu_idle2162 <idle>-0 3.N.1 11us : tick_nohz_idle_exit <-cpu_idle2206 <idle>-0 3.N.1 25us : sub_preempt_count <-cpu_idle2207 <idle>-0 3.N.. 25us : schedule <-cpu_idle2267 <idle>-0 2.N.2 3us : cpu_idle: state=4294967295 cpu_id=2
36 DEFINE_EVENT(cpu, cpu_idle,
1050 This option adds a write barrier to the cpu_idle loop so that,