On Thu, 2015-10-09 at 04:36:21 UTC, Paul Mackerras wrote:
> This fixes a race which can result in the same virtual IRQ number
> being assigned to two different MSI interrupts. The most visible
> consequence of that is usually a warning and stack trace from the
> sysfs code about an attempt to crea
On Thu, Sep 10, 2015 at 02:55:08PM +1000, Michael Ellerman wrote:
> On Thu, 2015-09-10 at 14:36 +1000, Paul Mackerras wrote:
> > This fixes a race which can result in the same virtual IRQ number
> > being assigned to two different MSI interrupts. The most visible
> > consequence of that is usually
On Thu, 2015-09-10 at 14:36 +1000, Paul Mackerras wrote:
> This fixes a race which can result in the same virtual IRQ number
> being assigned to two different MSI interrupts. The most visible
> consequence of that is usually a warning and stack trace from the
> sysfs code about an attempt to creat
This fixes a race which can result in the same virtual IRQ number
being assigned to two different MSI interrupts. The most visible
consequence of that is usually a warning and stack trace from the
sysfs code about an attempt to create a duplicate entry in sysfs.
The race happens when one CPU (say
