[Skiboot] [PATCH] phb4: Disable 32-bit MSI in capi mode
fbarrat at linux.ibm.com
Tue Aug 14 22:10:01 AEST 2018
If a capi device does a DMA write targeting an address lower than 4GB,
it does so through a 32-bit operation, per the PCI spec. In capi mode,
the first TVE entry is configured in bypass mode, so the address is
valid. But with any (bad) luck, the address could be 0xFFFFxxxx, thus
looking like a 32-bit MSI.
We currently enable both 32-bit and 64-bit MSIs, so the PHB will
interpret the DMA write as a MSI, which very likely results in an EEH
(MSI with a bad payload size).
We can fix it by disabling 32-bit MSI when switching the PHB to capi
mode. Capi devices are 64-bit.
Signed-off-by: Frederic Barrat <fbarrat at linux.ibm.com>
Stewart: this is for CORAL and is undergoing a round of testing on a
wider scale. It should only be merged once confirmed ok, hopefully
later this week.
hw/phb4.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/hw/phb4.c b/hw/phb4.c
index 6710d947..fbc8ddec 100644
@@ -4094,6 +4094,15 @@ static int64_t enable_capi_mode(struct phb4 *p, uint64_t pe_number,
for (i = 0; i < p->tvt_size; i++)
out_be64(p->regs + PHB_IODA_DATA0, p->tve_cache[i]);
+ * Since TVT#0 is in by-pass mode, disable 32-bit MSI, as a
+ * DMA write targeting 0x00000000FFFFxxxx would be interpreted
+ * as a 32-bit MSI
+ reg = in_be64(p->regs + PHB_PHB4_CONFIG);
+ reg &= ~PHB_PHB4C_32BIT_MSI_EN;
+ out_be64(p->regs + PHB_PHB4_CONFIG, reg);
/* set mbt bar to pass capi mmio window and keep the other
* mmio values
More information about the Skiboot