[+cc linux-pci] On Tue, Oct 25, 2011 at 9:36 AM, Steffen Persvold <sp@xxxxxxxxxxxxx> wrote: > On 10/25/2011 16:38, Bjorn Helgaas wrote: >> >> On Tue, Oct 18, 2011 at 2:22 AM, Daniel J Blueman >> <daniel@xxxxxxxxxxxxxxxxxx> wrote: >>> >>> Add quirk for Numascale's NumaChip to prevent resource conflicts. > > [] >> >> This feels like a band-aid ... what's the background here? I can see >> that you're disabling PCI resources, and I can read that this avoids >> conflicts, but what's the underlying cause of the conflict? >> >> I wonder if there's a more generic problem that should be fixed >> differently. Presumably the NumaChip designers put those BARs there >> for a reason, and often when we report "conflicts," it's really a clue >> that we're doing something wrong in host bridge discovery or in >> generic PCI. >> >> Can you post a complete dmesg log showing the conflict? >> > > Hi Bjorn, > > The issue is a bit complicated, but here's the story; NumaChip is a coherent > NorthBridge device on AMD systems (i.e part of the coherent fabric) but the > BIOS does *not* assign any resources to it, in fact the BIOS skips our > device entirely leaving our BAR registers at HW init values (0x00000000). > This is in fact by design (AMD AGESA code). This isn't really a big issue > for us anyway because we have other means of reaching our CSR logic (not > going into detail, but the other patches in this patchset would reveal how > we do that). > > Linux however, when scanning the PCI buses finds our device (because it is > responding to config space requests) it thinks that we got a BAR0 that > starts at 0x00000000 which obviously isn't correct. In addition, in the > bootloader that we've written for NumaChip systems (to bring them all > together as a huge coherent system) we had to use the expansion rom config > space register (F0x030) as kind of a "scratch register". We do treat zero as a special value when found in BARs, but that's sort of a muddy area. On x86, a zero-valued BAR is not very useful because typically there's RAM at address zero and PCI host bridges don't usually perform address translation. But on architectures like ia64/alpha/parisc/powerpc/etc., where host bridges often *do* translate addresses, zero might be a perfectly valid BAR value. > The end result is : > > [ 4.636297] pci 0000:00:1a.0: reg 10: [mem 0x00000000-0x000fffff] > [ 4.640317] pci 0000:00:1a.0: reg 30: [mem 0x3fff0000-0x3fffffff pref] > [ 4.644369] pci 0000:00:1a.1: [1b47:0602] type 0 class 0x000600 > > Neither of these resources are real, our device will not respond to requests > to any of those windows. > > The conflict we refer to in the patch is that since Linux thinks we have > those windows assigned to us, we get conflicts later on with real devices : > > [ 5.887856] pnp 00:0e: disabling [mem 0x00000000-0x0009ffff] because it > overlaps 0000:00:1a.0 BAR 0 [mem 0x00000000-0x000fffff] > [ 5.899525] pnp 00:0e: disabling [mem 0x000c0000-0x000cffff] because it > overlaps 0000:00:1a.0 BAR 0 [mem 0x00000000-0x000fffff] > [ 5.911002] pnp 00:0e: disabling [mem 0x000e0000-0x000fffff] because it > overlaps 0000:00:1a.0 BAR 0 [mem 0x00000000-0x000fffff] Yeah, this is gross, and this is definitely something Linux is doing wrong. We don't have a consistent way of marking PCI BARs as "disabled," so every zero-valued BAR seems to conflict with PNP devices. Typically there are motherboard devices like your 00:0e that reserve regions of low memory. Lots of machines complain like this, not just NumaChip, and there's no real ill effect. We say we're disabling a PNP device resource, but we don't actually evaluate an _SRS method to tell the BIOS to do anything. So I think we complain about the conflict but don't do anything else. > I guess technically, the Linux PCI bus probing code should check the Command > register (offset 0x4) to see if MemorySpace is enabled (which in our case it > won't be) before checking the BAR registers. The question is how we handle a device with MemorySpace disabled. In most cases, I think we want to assign BAR resources to it so that if a driver claims the device, we can enable MemorySpace and the device will work. If the BIOS leaves MemorySpace disabled and Linux doesn't assign BAR space at boot-time, we may be stuck because in general we can't assign resources dynamically. Dynamic assignment might require moving other devices, enlarging bridge windows, etc., which Linux currently doesn't support. NumaChip sounds like an exception because you know you never care about using those BARs. But I'm curious -- it looks like Linux didn't even try to assign resources to them. I thought something in the pci_assign_unassigned_resources() path would have tried to do something with them. If we *did* assign resources to those BARs, I assume nothing would break, since there's no driver that actually uses them. Right? Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
