On Mon, Dec 18, 2023 at 10:38:52PM -0500, Joel Fernandes wrote:
> On Tue, Dec 19, 2023 at 12:19:15AM +0100, Frederic Weisbecker wrote:
> > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > index 3ac3c846105f..157f3ca2a9b5 100644
> > --- a/kernel/rcu/tree.c
> > +++ b/kernel/rcu/tree.c
> > @@ -1013,6 +1013,38 @@ static bool rcu_future_gp_cleanup(struct rcu_node *rnp)
> > return needmore;
> > }
> >
> > +static void swake_up_one_online_ipi(void *arg)
> > +{
> > + struct swait_queue_head *wqh = arg;
> > +
> > + swake_up_one(wqh);
> > +}
>
> Speaking of, the scheduler refuses to do remote-IPI-style wakeups
> (TTWU_QUEUE) whenever the destination CPU is in a hotplug state.
>
> static inline bool ttwu_queue_cond(struct task_struct *p, int cpu)
> {
> /*
> * Do not complicate things with the async wake_list while the CPU is
> * in hotplug state.
> */
> if (!cpu_active(cpu))
> return false;
> ...
> }
Yes, because all irrelevant tasks must be migrated out upon
CPUHP_AP_SCHED_WAIT_EMPTY, thanks to balance_push_set().
(Though right now I'm missing the flush_smp_call_function_queue() call that flushes
the ttwu queue between sched_cpu_deactivate() and sched_cpu_wait_empty())
>
> Along these lines, I wonder if, it is safe to do a wakeup in this fashion (as
> done by this patch) if the destination CPU was also going down.
>
> Also the same ttwu_queue_cond() checks for CPU affinities before deciding to
> not do the IPI-style queue.
>
> /* Ensure the task will still be allowed to run on the CPU. */
> if (!cpumask_test_cpu(cpu, p->cpus_ptr))
> return false;
>
> Not that anyone should be changing RCU thread priorities around while the IPI
> is in flight, but...
>
> I wonder if the reason TTWU is excessively paranoid is that the IPI can be
> delayed for example, leading to race conditions.
It's because nothing irrelevant must be queued after sched_cpu_wait_empty().
But note this patch does something different, it doesn't defer the runqueue
enqueue like ttwu queue does. It defers the whole actual wakeup. This means that the
decision as to where to queue the task is delegated to an online CPU. So it's
not the same constraints. Waking up a task _from_ a CPU that is active or not but
at least online is supposed to be fine.
Thanks.
