Re: [PATCH 1/2] irq_work: Fix racy IRQ_WORK_BUSY flag setting

2012-11-13 Thread Steven Rostedt
On Fri, 2012-11-02 at 18:35 +0100, Frederic Weisbecker wrote: > The IRQ_WORK_BUSY flag is set right before we execute the > work. Once this flag value is set, the work enters a > claimable state again. > > So if we have specific data to compute in our work, we ensure it's > either handled by

Re: [PATCH 1/2] irq_work: Fix racy IRQ_WORK_BUSY flag setting

2012-11-13 Thread Steven Rostedt
On Fri, 2012-11-02 at 18:35 +0100, Frederic Weisbecker wrote: The IRQ_WORK_BUSY flag is set right before we execute the work. Once this flag value is set, the work enters a claimable state again. So if we have specific data to compute in our work, we ensure it's either handled by another

[PATCH 1/2] irq_work: Fix racy IRQ_WORK_BUSY flag setting

2012-11-02 Thread Frederic Weisbecker
The IRQ_WORK_BUSY flag is set right before we execute the work. Once this flag value is set, the work enters a claimable state again. So if we have specific data to compute in our work, we ensure it's either handled by another CPU or locally by enqueuing the work again. This state machine is

[PATCH 1/2] irq_work: Fix racy IRQ_WORK_BUSY flag setting

2012-11-02 Thread Frederic Weisbecker
The IRQ_WORK_BUSY flag is set right before we execute the work. Once this flag value is set, the work enters a claimable state again. So if we have specific data to compute in our work, we ensure it's either handled by another CPU or locally by enqueuing the work again. This state machine is