> I think the right way to fix this is to ensure mmio write ordering in > the pci_write_config_*() implementations. Like this. I'm happy to fix this in the PCI core and not force drivers to worry about this. John, can you confirm that this patch fixes the issue for you? Thanks, Roland - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Ordering between PCI config space writes and MMIO reads?
- From: Matthew Wilcox <[email protected]>
- Re: Ordering between PCI config space writes and MMIO reads?
- From: John Partridge <[email protected]>
- Re: Ordering between PCI config space writes and MMIO reads?
- References:
- Ordering between PCI config space writes and MMIO reads?
- From: Roland Dreier <[email protected]>
- Re: Ordering between PCI config space writes and MMIO reads?
- From: Jeff Garzik <[email protected]>
- Re: Ordering between PCI config space writes and MMIO reads?
- From: Matthew Wilcox <[email protected]>
- Ordering between PCI config space writes and MMIO reads?
- Prev by Date: Re: Ordering between PCI config space writes and MMIO reads?
- Next by Date: [PATCH] s2io: add PCI error recovery support
- Previous by thread: Re: Ordering between PCI config space writes and MMIO reads?
- Next by thread: Re: Ordering between PCI config space writes and MMIO reads?
- Index(es):
 |