>>> On 25.03.15 at 19:12, wrote:
>> Changing the affinity of non-maskable MSI IRQs seems bogus too
>
> Agreed. Their affinity can clearly only be changed safely by a device
> driver which can guarantee that an interrupt will not be generated
> during the vulnerable period.
>
> This further im
On 20/03/15 16:40, Jan Beulich wrote:
With ->startup unmasking the IRQ, setting the affinity afterwards
without masking the IRQ again is invalid namely for MSI (which can't
have their affinity updated atomically).
Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
---
Changing the affini
>>> On 23.03.15 at 19:46, wrote:
> On Fri, Mar 20, 2015 at 03:40:02PM +, Jan Beulich wrote:
>> With ->startup unmasking the IRQ, setting the affinity afterwards
>> without masking the IRQ again is invalid namely for MSI (which can't
>> have their affinity updated atomically).
>
> That took a
On Fri, Mar 20, 2015 at 03:40:02PM +, Jan Beulich wrote:
> With ->startup unmasking the IRQ, setting the affinity afterwards
> without masking the IRQ again is invalid namely for MSI (which can't
> have their affinity updated atomically).
That took a bit of verification :-)
Could you include
