[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH] AMD/iommu: SR56x0 Erratum 64 - Reset Command and Event head & tail pointers
Reference at time of patch: http://support.amd.com/us/ChipsetMotherboard_TechDocs/46303.pdf Erratum 64 states that the head and tail pointers for the Command buffer and Event log are only reset on a cold boot, not a warm boot. While the erratum is limited to systems using SR56xx chipsets (such as Family 10h CPUs), resetting the pointers is a sensible action in all cases. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> -- The code appears to lack an MMIO 64bit write function which would be the correct solution here. However, for these four registers, bit 19 is the highest non-reserved bit, meaning that the writel() will do the correct thing. I suspect that a writeq() function would make a huge difference to the legibility and brevity of this code. diff -r 2369a9d759f0 -r e1a69214aff3 xen/drivers/passthrough/amd/iommu_init.c --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -154,6 +154,15 @@ static void register_iommu_cmd_buffer_in IOMMU_CMD_BUFFER_LENGTH_MASK, IOMMU_CMD_BUFFER_LENGTH_SHIFT, &entry); writel(entry, iommu->mmio_base+IOMMU_CMD_BUFFER_BASE_HIGH_OFFSET); + + /* AMD SR56x0 Erratum 64. CMD buffer head and tail pointers are not reset + * on warm boot. A newer BIOS may or may not do this for us, as per the + * workaround advise. + * + * However, it is a safe and sensible action to perform unconditionally. + */ + writel(0, iommu->mmio_base + IOMMU_CMD_BUFFER_HEAD_OFFSET); + writel(0, iommu->mmio_base + IOMMU_CMD_BUFFER_TAIL_OFFSET); } static void register_iommu_event_log_in_mmio_space(struct amd_iommu *iommu) @@ -182,6 +191,15 @@ static void register_iommu_event_log_in_ IOMMU_EVENT_LOG_LENGTH_MASK, IOMMU_EVENT_LOG_LENGTH_SHIFT, &entry); writel(entry, iommu->mmio_base+IOMMU_EVENT_LOG_BASE_HIGH_OFFSET); + + /* AMD SR56x0 Erratum 64. Event log head and tail pointers are not reset + * on warm boot. A newer BIOS may or may not do this for us, as per the + * workaround advise. + * + * However, it is a safe and sensible action to perform unconditionally. + */ + writel(0, iommu->mmio_base + IOMMU_EVENT_LOG_HEAD_OFFSET); + writel(0, iommu->mmio_base + IOMMU_EVENT_LOG_TAIL_OFFSET); } static void register_iommu_ppr_log_in_mmio_space(struct amd_iommu *iommu) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |