cxl: Keep IRQ mappings on context teardown

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 is never EOIed. The lost of EOI results in all subsequent
mappings to the same HW IRQ never receiving an interrupt.

We've seen this race with cxl test cases which are doing heavy context
startup and teardown at the same time as heavy interrupt load.

A fix to the generic code is being investigated also.

Signed-off-by: Michael Neuling <[e-mail]>
Cc: [e-mail] # 3.8
Tested-by: Andrew Donnellan <[e-mail]>
Acked-by: Ian Munsie <[e-mail]>
Tested-by: Vaibhav Jain <[e-mail]>
Signed-off-by: Michael Ellerman <[e-mail]>

drivers/misc/cxl/irq.c

···
 void cxl_unmap_irq(unsigned int virq, void *cookie)
 {
 	free_irq(virq, cookie);
-	irq_dispose_mapping(virq);
 }
 
 int cxl_register_one_irq(struct cxl *adapter,