From: Vijay Kumar <vijay.ac.kumar@xxxxxxxxxx>Yes, I see your point.
Date: Thu, 20 Jul 2017 22:36:42 -0500
I can give a try :). But looks to me one thing that will go wrong isActually, the bigger problem is that scheduler_ipi() can raise a
irq accounting done in __irq_enter() and rcu_irq_enter().
software interrupt, and nothing will invoke it.
It's turning quite ugly to avoid the IRQ overhead, I must admit.
So ignore this for now.
In the longer term a probably cleaner way to do this is to have
a special direct version of scheduler_ipi() that invokes all the
necessary work, even the rebalance softirq, directly rather than
indirectly.