LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* About Full c3-stop status.
@ 2021-09-10  1:20 Yun Levi
  0 siblings, 0 replies; only message in thread
From: Yun Levi @ 2021-09-10  1:20 UTC (permalink / raw)
  To: Thomas Gleixner, preeti, mingo, rmk+lkml, dmitri.vorobiev
  Cc: youngjun.park, Linux Kernel Mailing List

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.

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2021-09-10  1:23 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-10  1:20 About Full c3-stop status Yun Levi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).