On Wed, 2013-05-22 at 09:59 -0700, Yinghai Lu wrote: > On Wed, May 22, 2013 at 7:54 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > > What exactly is the problem here? Is it just that you don't want to > > see the "can't assign" messages? Or is there a device with a BAR that > > *should* be assigned, but isn't? If so, which device is it? > > We try must+optional as first, then if there is any ioport or mmio fail > we will stick to must only then extend must to meet optional. > but mmio range and mmio-pref could be connected each other, > so extend will fail... > > problem here, some root bus will not have ioport range, so it will always have > ioport allocation fail. > > looks like right fix for v3.9 should be as attached patch. > it will keep must+optional for mmio, if only ioport fails.... The simpler thing to do would have been to do the entire thing in two separate passes, one for MMIO and one for IO, and skip the second one entirely if there's no IO at the host bridge level :-) Cheers, Ben. -- 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
