From 9cd69214a129c36016fd3294f5219fa47a50404c Mon Sep 17 00:00:00 2001 From: Benjamin Herrenschmidt Date: Tue, 12 Dec 2017 16:22:52 +1100 Subject: xive: Do not return a trigger page for an escalation interrupt This is bogus, we don't support them. (Thankfully the callers didn't actually try to use this on escalation interrupts). Signed-off-by: Benjamin Herrenschmidt Tested-by: Oliver O'Halloran Signed-off-by: Stewart Smith (cherry picked from commit 3e7f04a7398a5dcb38ff11d0b11f630630a3bb74) Signed-off-by: Stewart Smith --- hw/xive.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/xive.c b/hw/xive.c index cd748fc..f708cf3 100644 --- a/hw/xive.c +++ b/hw/xive.c @@ -2092,8 +2092,8 @@ void *xive_get_trigger_port(uint32_t girq) return NULL; if (GIRQ_IS_ESCALATION(girq)) { - /* Page 2 of the EQ MMIO space is the escalate irq */ - return x->eq_mmio + idx * 0x20000 + 0x10000; + /* There is no trigger page for escalation interrupts */ + return NULL; } else { /* Make sure it's an IPI on that chip */ if (girq < x->int_base || -- cgit v1.1