[PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-17 Thread Frederic Weisbecker
On irq work initialization, let the user choose to define it as "lazy" or not. "Lazy" means that we don't want to send an IPI (provided the arch can anyway) when we enqueue this work but we rather prefer to wait for the next timer tick to execute our work if possible. This is going to be a

[PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-17 Thread Frederic Weisbecker
On irq work initialization, let the user choose to define it as lazy or not. Lazy means that we don't want to send an IPI (provided the arch can anyway) when we enqueue this work but we rather prefer to wait for the next timer tick to execute our work if possible. This is going to be a benefit

Re: [PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-16 Thread Frederic Weisbecker
2012/11/16 Steven Rostedt : > On Fri, 2012-11-16 at 03:21 +0100, Frederic Weisbecker wrote: >> >> /* >> * Claim the entry so that no one else will poke at it. >> @@ -68,14 +59,18 @@ void __weak arch_irq_work_raise(void) >> */ >> static void __irq_work_queue(struct irq_work *work) >> { >> -

Re: [PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-16 Thread Steven Rostedt
On Fri, 2012-11-16 at 03:21 +0100, Frederic Weisbecker wrote: > > /* > * Claim the entry so that no one else will poke at it. > @@ -68,14 +59,18 @@ void __weak arch_irq_work_raise(void) > */ > static void __irq_work_queue(struct irq_work *work) > { > - bool empty; > - >

Re: [PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-16 Thread Steven Rostedt
On Fri, 2012-11-16 at 03:21 +0100, Frederic Weisbecker wrote: /* * Claim the entry so that no one else will poke at it. @@ -68,14 +59,18 @@ void __weak arch_irq_work_raise(void) */ static void __irq_work_queue(struct irq_work *work) { - bool empty; - preempt_disable();

Re: [PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-16 Thread Frederic Weisbecker
2012/11/16 Steven Rostedt rost...@goodmis.org: On Fri, 2012-11-16 at 03:21 +0100, Frederic Weisbecker wrote: /* * Claim the entry so that no one else will poke at it. @@ -68,14 +59,18 @@ void __weak arch_irq_work_raise(void) */ static void __irq_work_queue(struct irq_work *work) {

[PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-15 Thread Frederic Weisbecker
On irq work initialization, let the user choose to define it as "lazy" or not. "Lazy" means that we don't want to send an IPI (provided the arch can anyway) when we enqueue this work but we rather prefer to wait for the next timer tick to execute our work if possible. This is going to be a

[PATCH 8/9] irq_work: Make self-IPIs optable

2012-11-15 Thread Frederic Weisbecker
On irq work initialization, let the user choose to define it as lazy or not. Lazy means that we don't want to send an IPI (provided the arch can anyway) when we enqueue this work but we rather prefer to wait for the next timer tick to execute our work if possible. This is going to be a benefit