powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx
PATCH v3 1/1 powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx
A PCIe erratum of mpc85xx may causes a core hang when a link of PCIe goes down. when the link goes down, Non-posted transactions issued via the ATMU requiring completion result in an instruction stall. At the same time a machine-check exception is generated to the core to allow further processing by the handler. We implements the handler which skips the instruction caused the stall.
---
V3 changed: Just rebase the patch.
arch/powerpc/kernel/cpu_setup_fsl_booke.S | 2 +- arch/powerpc/kernel/traps.c | 3 ++ arch/powerpc/sysdev/fsl_pci.c | 39 +++++++++++++++++++++++++++++ arch/powerpc/sysdev/fsl_pci.h | 6 ++++ 4 files changed, 49 insertions(+), 1 deletions(-)
arch/powerpc/kernel/cpu_setup_fsl_booke.S +1 -1
@@ -64,7 +64,7 @@ _GLOBAL(__setup_cpu_e500v2) bl __e500_icache_setup bl __e500_dcache_setup bl __setup_e500_ivors -#ifdef CONFIG_FSL_RIO +#if defined(CONFIG_FSL_RIO) || defined(CONFIG_FSL_PCI) /* Ensure that RFXE is set */ mfspr r3,SPRN_HID1 oris r3,r3,HID1_RFXE@h
arch/powerpc/kernel/traps.c +3 -0
@@ -59,6 +59,7 @@#include <asm/fadump.h> #include <asm/switch_to.h> #include <asm/debug.h> +#include <sysdev/fsl_pci.h> #if defined(CONFIG_DEBUGGER ) || defined(CONFIG_KEXEC )int (*__debugger)(struct pt_regs *regs)__read_mostly ;
@@ -555,6 +556,8 @@ int machine_check_e500(struct pt_regs *regs)if (reason &MCSR_BUS_RBERR ) {if (fsl_rio_mcheck_exception (regs))return 1 ; +if (fsl_pci_mcheck_exception (regs)) +return 1 ; }printk ("Machine check in kernel mode.\n" );
arch/powerpc/sysdev/fsl_pci.c +39 -0
@@ -30,6 +30,7 @@#include <asm/io.h> #include <asm/prom.h> #include <asm/pci-bridge.h> +#include <asm/ppc-pci.h> #include <asm/machdep.h> #include <sysdev/fsl_soc.h> #include <sysdev/fsl_pci.h>
@@ -808,6 +809,44 @@ u64 fsl_pci_immrbar_base(struct pci_controller *hose)return 0 ; } +static int is_in_pci_mem_space (phys_addr_t addr) +{ +struct pci_controller *hose; +struct resource *res; +int i; + +list_for_each_entry (hose, &hose_list, list_node) { +if (!early_find_capability (hose,0 ,0 ,PCI_CAP_ID_EXP )) +continue ; + +for (i =0 ; i <3 ; i++) { + res = &hose->mem_resources[i]; +if ((res->flags &IORESOURCE_MEM ) && + addr >= res->start && addr <= res->end) +return 1 ; + } + } +return 0 ; +} + +int fsl_pci_mcheck_exception (struct pt_regs *regs) +{ +phys_addr_t addr =0 ; + +#ifdef CONFIG_PHYS_64BIT + addr =mfspr (SPRN_MCARU ); + addr <<=32 ; +#endif + addr +=mfspr (SPRN_MCAR ); + +if (is_in_pci_mem_space (addr)) { + regs->nip +=4 ; +return 1 ; + } + +return 0 ; +} +#if defined(CONFIG_FSL_SOC_BOOKE ) || defined(CONFIG_PPC_86xx)static const struct of_device_id pci_ids[] = { { .compatible = "fsl,mpc8540-pci", },
arch/powerpc/sysdev/fsl_pci.h +6 -0
@@ -101,5 +101,11 @@ void fsl_pci_init(void);static inline void fsl_pci_init (void ) {}#endif +#ifdef CONFIG_FSL_PCI +extern int fsl_pci_mcheck_exception (struct pt_regs *); +#else +static inline int fsl_pci_mcheck_exception (struct pt_regs *regs) {return 0 ; } +#endif +#endif /* __POWERPC_FSL_PCI_H */ #endif /* __KERNEL__ */
Signature · 1 line
1.7.5.1
Quoted 6 lines
A PCIe erratum of mpc85xx may causes a core hang when a link of PCIe goes down. when the link goes down, Non-posted transactions issued via the ATMU requiring completion result in an instruction stall. At the same time a machine-check exception is generated to the core to allow further processing by the handler. We implements the handler which skips the instruction caused the stall.
Does skipping the faulting instruction really help?
We use the mpc83xx and have seen PCIe issues that may be related to a documented errata in the CSB-PEX bridge (which I can't find my copy of).
Do the 85xx and 83xx have the same PCIe block? Recovery from it seems almost impossible - my interpretation was that you have to hard reset the PCIe block and rewrite the entire configuration.
The problem we see happens during some PEX DMA transfers (possibly due to issues with the target), the DMA doesn't complete and any further PIO transfers fault (and panic). Unfortunately the PEX has no documented status registers, so it is difficult to determine what is (or rather isn't) Happening.
David