On Thu, 10 Apr 2025 12:10:19 -0700 "Paul E. McKenney" <[email protected]> wrote:
> There is some in-kernel support for turning the rcu_nocbs portion > of nohz_full on and off on a per-CPU basis, but a given CPU must be > offline in order to do this transition. Last I heard, there are still > issues preventing this support from being generalized to cover all of > the nohz_full functionality, and I doubt that it would be exposed to > user level until all of nohz_full is supported. > > The rcu_nocbs in-kernel functionality is tested regularly. > > Are you interested in working on joining the noble quest of getting the > rest of the nohz_full support in place? (Full disclosure: This stuff > is non-trivial.) I believe the request is more of just tracing entry and exit from the kernel, which just needs a simple trace event at the border crossings. NOHZ_FULL is to allow the kernel infrastructure to know that a CPU has transitioned states (no need to do RCU or have a tick on that CPU). That's a much harder task as you not only need to know the border crossings, you also need to make sure nothing happens from the locations you mark and the crossing takes place. That's a much more difficult task. -- Steve
