On Wed, Oct 28, 2020 at 02:40:46PM +0100, Frederic Weisbecker wrote:
> On Wed, Oct 28, 2020 at 12:07:12PM +0100, Peter Zijlstra wrote:
> > While the traditional irq_work relies on the ability to self-IPI, it
> > makes sense to provide an unconditional irq_work_queue_remote()
> > interface.
>
> We
On Wed, Oct 28, 2020 at 03:53:24PM +0100, Peter Zijlstra wrote:
> On Wed, Oct 28, 2020 at 02:40:46PM +0100, Frederic Weisbecker wrote:
> > On Wed, Oct 28, 2020 at 12:07:12PM +0100, Peter Zijlstra wrote:
> > > While the traditional irq_work relies on the ability to self-IPI, it
> > > makes sense to
On Wed, Oct 28, 2020 at 12:07:12PM +0100, Peter Zijlstra wrote:
> While the traditional irq_work relies on the ability to self-IPI, it
> makes sense to provide an unconditional irq_work_queue_remote()
> interface.
We may need a reason as well here.
> --- a/kernel/rcu/tree.c
> +++
While the traditional irq_work relies on the ability to self-IPI, it
makes sense to provide an unconditional irq_work_queue_remote()
interface.
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/irq_work.h | 17 --
kernel/irq_work.c| 129
On Wed, Oct 28, 2020 at 02:40:46PM +0100, Frederic Weisbecker wrote:
> On Wed, Oct 28, 2020 at 12:07:12PM +0100, Peter Zijlstra wrote:
> > While the traditional irq_work relies on the ability to self-IPI, it
> > makes sense to provide an unconditional irq_work_queue_remote()
> > interface.
>
> We
5 matches
Mail list logo