Re: [1/2] cxl: Keep IRQ mappings on context teardown

2016-04-27 Thread Michael Ellerman
On Fri, 2016-22-04 at 04:57:48 UTC, Michael Neuling wrote: > Keep IRQ mappings on context teardown. This won't leak IRQs as if we > allocate the mapping again, the generic code will give the same > mapping used last time. > > Doing this works around a race in the generic code. Masking the > inter

Re: [PATCH 1/2] cxl: Keep IRQ mappings on context teardown

2016-04-21 Thread Vaibhav Jain
Michael Neuling writes: > Keep IRQ mappings on context teardown. This won't leak IRQs as if we > allocate the mapping again, the generic code will give the same > mapping used last time. > > Doing this works around a race in the generic code. Masking the > interrupt introduces a race which can c

Re: [PATCH 1/2] cxl: Keep IRQ mappings on context teardown

2016-04-21 Thread Ian Munsie
Acked-by: Ian Munsie ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: [PATCH 1/2] cxl: Keep IRQ mappings on context teardown

2016-04-21 Thread Andrew Donnellan
On 22/04/16 14:57, Michael Neuling wrote: Keep IRQ mappings on context teardown. This won't leak IRQs as if we allocate the mapping again, the generic code will give the same mapping used last time. Doing this works around a race in the generic code. Masking the interrupt introduces a race whic

[PATCH 1/2] cxl: Keep IRQ mappings on context teardown

2016-04-21 Thread Michael Neuling
Keep IRQ mappings on context teardown. This won't leak IRQs as if we allocate the mapping again, the generic code will give the same mapping used last time. Doing this works around a race in the generic code. Masking the interrupt introduces a race which can crash the kernel or result in IRQ that