[PATCH v2] arm64: SMMU-v2: Workaround for Cavium ThunderX erratum 28168
Marc Zyngier
marc.zyngier at arm.com
Wed Nov 16 01:54:35 PST 2016
On 15/11/16 18:24, David Daney wrote:
> On 11/15/2016 01:26 AM, Marc Zyngier wrote:
>> On 15/11/16 07:00, Geetha sowjanya wrote:
>>> From: Tirumalesh Chalamarla <Tirumalesh.Chalamarla at cavium.com>
>>>
>>> This patch implements Cavium ThunderX erratum 28168.
>>>
>>> PCI requires stores complete in order. Due to erratum #28168
>>> PCI-inbound MSI-X store to the interrupt controller are delivered
>>> to the interrupt controller before older PCI-inbound memory stores
>>> are committed.
>>> Doing a sync on SMMU will make sure all prior data transfers are
>>> completed before invoking ISR.
>>>
>>> Signed-off-by: Tirumalesh Chalamarla <Tirumalesh.Chalamarla at cavium.com>
>>> Signed-off-by: Geetha sowjanya <gakula at caviumnetworks.com>
> [...]
>>> --- a/drivers/irqchip/irq-gic-v3.c
>>> +++ b/drivers/irqchip/irq-gic-v3.c
>>> @@ -28,6 +28,8 @@
>>> #include <linux/of_irq.h>
>>> #include <linux/percpu.h>
>>> #include <linux/slab.h>
>>> +#include <linux/msi.h>
>>> +#include <linux/pci.h>
>>>
>>> #include <linux/irqchip.h>
>>> #include <linux/irqchip/arm-gic-common.h>
>>> @@ -736,6 +738,20 @@ static inline void gic_cpu_pm_init(void) { }
>>>
>>> #define GIC_ID_NR (1U << gic_data.rdists.id_bits)
>>>
>>> +/*
>>> + * Due to #28168 erratum in ThunderX,
>>> + * we need to make sure DMA data transfer is done before MSIX.
>>> + */
>>> +static void cavium_irq_perflow_handler(struct irq_data *data)
>>> +{
>>> + struct pci_dev *pdev;
>>> +
>>> + pdev = msi_desc_to_pci_dev(irq_data_get_msi_desc(data));
>>
>> What happens if this is not a PCI device?
>>
>>> + if ((pdev->vendor != 0x177d) &&
>>> + ((pdev->device & 0xA000) != 0xA000))
>>> + cavium_arm_smmu_tlb_sync(&pdev->dev);
>>
>> I've asked that before. What makes Cavium devices so special that they
>> are not sensitive to this bug?
>
>
> This is a heuristic for devices connected to external PCIe buses as
> opposed to on-SoC devices (which don't suffer from the erratum).
>
> In any event what would happen if we got rid of this check and ...
>
>
>>
>>> +}
>>> +
>>> static int gic_irq_domain_map(struct irq_domain *d, unsigned int irq,
>>> irq_hw_number_t hw)
>>> {
>>> @@ -773,6 +789,9 @@ static int gic_irq_domain_map(struct irq_domain *d, unsigned int irq,
>>> return -EPERM;
>>> irq_domain_set_info(d, irq, hw, chip, d->host_data,
>>> handle_fasteoi_irq, NULL, NULL);
>>> + if (cpus_have_cap(ARM64_WORKAROUND_CAVIUM_28168))
>>> + __irq_set_preflow_handler(irq,
>>> + cavium_irq_perflow_handler);
>>
>
> ... move the registration of the preflow_handler into a
> msi_domain_ops.msi_finish() handler in irq-git-v3-its-pic-msi.c?
That's the kind of thing I was angling for. You'll have to store the
device pointer into the scratchpad (we still have plenty of space there)
so that msi_finish() can have a peek.
> There we will know that it is a pci device, and can walk up the bus
> hierarchy to see if there is a Cavium PCIe root port present. If such a
> port is found, we know we are on an external Cavium PCIe bus, and can
> register the preflow_handler without having to check the device identifiers.
Something like that (though I'm unclear why other devices wouldn't see a
root port, but that's probably me lacking some PCIe foo).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
More information about the linux-arm-kernel
mailing list