From mboxrd@z Thu Jan 1 00:00:00 1970 From: matthew_minter@xyratex.com (Matthew Minter) Date: Tue, 8 Apr 2014 21:17:47 +0100 Subject: Intel I350 mini-PCIe card (igb) on Mirabox (mvebu / Armada 370) In-Reply-To: <20140408192141.GH32490@obsidianresearch.com> References: <20140405193435.50d8dd81@skate> <54BB31A2B04145E8908E0183FAB6B61B@fatboyfat.co.uk> <20140408171309.09bbf968@skate> <20140408174034.79df403e@skate> <20140408175545.1b4d55a5@skate> <20140408171417.GB27776@obsidianresearch.com> <20140408175324.GH11052@1wt.eu> <20140408180828.GC32490@obsidianresearch.com> <20140408191514.GJ11052@1wt.eu> <20140408192141.GH32490@obsidianresearch.com> Message-ID: <2FF5F2FD-2DAC-4E51-87A0-90DBAFE6AA01@xyratex.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org This is just a guess but perhaps the best we could do would be to round up but also add logic to fail completely if adding a PCI device would cause a window to overlap? This would mean situations will be fixed where we can without design changes and situations that cannot be fixed will fail with clear errors? On 8 Apr 2014, at 20:21, Jason Gunthorpe wrote: > On Tue, Apr 08, 2014 at 09:15:14PM +0200, Willy Tarreau wrote: > >> OK that's what I understood, but I mean why rounding down instead of up >> in order to correctly cover the window the device expects ? And we all >> found that rounding up fixed our respective devices (3 igb NICs, one >> myri10ge NIC, one SATA controller I believe). >> >> By rounding up you'd have had 1ffffff instead, which at least covers the >> window the device expects. > > It is also an error to configure the mbus to have overlaping windows > and the code checks for overlaps with the base/size given. If we round > up then it might create an overlap. > > You guys were OK with the round up in the PCI code only because your > systems have a single used PEX so the rounding didn't create an > overlaping situation.. > > The generic code should either round down, or compeltely bail, as > Thomas suggested. > > Fundementally we shouldn't get to the WARN_ON, so what happens after > is just an attempt to salvage something from the situation. > > Jason -- ------------------------------ For additional information including the registered office and the treatment of Xyratex confidential information please visit www.xyratex.com ------------------------------