lkml.org 
[lkml]   [2021]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectAbout Full c3-stop status.
Hi all.

Sorry to interrupt you but I have a question while I am reading the
tick-broadcast codes.

When a cpu goes to c3-stop, I confirm it calls the
tick_broadcast_enter function with TICK_BROADCAST_ENTER.

While entering, it calls the broadcast_needs_cpu with current cpu.

In the last condition of broadcast_needs_cpu, it checks whether the
broadcast device is bound on this cpu.

However, except the ce_broadcast_hrtimer in tick-broadcast-hrtimer.c,
all other real devices set bound_on fields as 0, Therefore, it seems
that cpu 0 couldn't enter c3-stop though it has the feature.

My question is
1. Couldn't cpu 0 enter c3-stop?
2. If true, why don't we set bound_on fields specifically?

Thanks.

HTH.
Levi.

\
 
 \ /
  Last update: 2021-09-10 03:24    [W:0.032 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site