xen/events: avoid using info_for_irq() in xen_send_IPI_one()
authorJuergen Gross <jgross@suse.com>
Tue, 24 Oct 2023 11:51:36 +0000 (13:51 +0200)
committerJuergen Gross <jgross@suse.com>
Mon, 13 Nov 2023 06:22:00 +0000 (07:22 +0100)
commite64e7c74b99ec9e439abca75f522f4b98f220bd1
treebf1beaabc09842d03aa36ae4307e3ec00d7620d6
parentb85ea95d086471afb4ad062012a4d73cd328fa86
xen/events: avoid using info_for_irq() in xen_send_IPI_one()

xen_send_IPI_one() is being used by cpuhp_report_idle_dead() after
it calls rcu_report_dead(), meaning that any RCU usage by
xen_send_IPI_one() is a bad idea.

Unfortunately xen_send_IPI_one() is using notify_remote_via_irq()
today, which is using irq_get_chip_data() via info_for_irq(). And
irq_get_chip_data() in turn is using a maple-tree lookup requiring
RCU.

Avoid this problem by caching the ipi event channels in another
percpu variable, allowing the use notify_remote_via_evtchn() in
xen_send_IPI_one().

Fixes: 721255b9826b ("genirq: Use a maple tree for interrupt descriptor management")
Reported-by: David Woodhouse <dwmw@amazon.co.uk>
Signed-off-by: Juergen Gross <jgross@suse.com>
Tested-by: David Woodhouse <dwmw@amazon.co.uk>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Juergen Gross <jgross@suse.com>
drivers/xen/events/events_base.c