On 21.08.20 09:15, Sergey Temerkhanov wrote:
Use a dedicated pointer for IRQ data to avoid conflicts with some
other parts of the kernel code which my use handler_data for their
own purposes while still running on Xen
Sergey Temerkhanov (2):
Xen: Use a dedicated irq_info structure pointer
Xen: Rename irq_info structure
drivers/xen/events/events_2l.c | 2 +-
drivers/xen/events/events_base.c | 80 +++++++++++++---------------
drivers/xen/events/events_fifo.c | 5 +-
drivers/xen/events/events_internal.h | 12 ++---
include/linux/irq.h | 17 ++++++
kernel/irq/chip.c | 14 +++++
6 files changed, 78 insertions(+), 52 deletions(-)
Did you see any specific problem where handler_data is written by
another component?
In case this is a real problem I don't think your approach will be
accepted, especially the IRQ subsystem maintainers probably won't
like it.
And please include the maintainers of the files you are modifying in
the recipients list of the patch(es).
Juergen
