Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1613267 > unrolled thread
| Started by | Will Deacon <will.deacon@arm.com> |
|---|---|
| First post | 2017-03-30 18:30 +0200 |
| Last post | 2017-03-30 18:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2 07/22] PCI: ECAM: use ioremap_nopost() to map config region Will Deacon <will.deacon@arm.com> - 2017-03-30 18:30 +0200
| From | Will Deacon <will.deacon@arm.com> |
|---|---|
| Date | 2017-03-30 18:30 +0200 |
| Subject | Re: [PATCH v2 07/22] PCI: ECAM: use ioremap_nopost() to map config region |
| Message-ID | <tqL7s-AJ-9@gated-at.bofh.it> |
On Mon, Mar 27, 2017 at 10:49:35AM +0100, Lorenzo Pieralisi wrote: > Current ECAM kernel implementation uses ioremap() to map the ECAM > configuration space memory region; this is not safe in that on some > architectures the ioremap interface provides mappings that allow posted > write transactions. This, as highlighted in the PCIe specifications > (4.0 - Rev0.3, "Ordering Considerations for the Enhanced Configuration > Address Mechanism"), can create ordering issues for software because > posted writes transactions on the CPU host bus are non posted in the > PCI express fabric. > > Update the ioremap() interface to use ioremap_nopost() whose > mapping attributes guarantee that non-posted writes transactions > are issued for memory writes within the ECAM memory mapped address > region. > > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> > Cc: Bjorn Helgaas <bhelgaas@google.com> > --- > drivers/pci/ecam.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) Acked-by: Will Deacon <will.deacon@arm.com> Will
Back to top | Article view | linux.kernel
csiph-web