On Fri, Feb 15, 2013 at 09:26:09AM -0700, Bjorn Helgaas wrote: > On Thu, Feb 14, 2013 at 10:06 PM, Thomas Petazzoni > <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote: > > >> > + case PCI_PREF_LIMIT_UPPER32: > >> > + bridge->preflimitupper = value; > >> > + break; > >> > >> You're relying on a subsequent PCI_COMMAND write to set PCI_COMMAND_IO > >> and/or PCI_COMMAND_MEMORY, and you program the bridge windows at that > >> time. > > > > Correct. > > > >> It might be a good idea if the PCI core did clear those bits > >> while updating the windows, but I'm not sure we do. In any case, > >> delaying the update is a difference from a standard P2P bridge that > >> could cause issues later. > > > > When would you want the window assignment to occur? Directly when the > > registers containing the base/limit are being written to? There are > > multiple registers for base/limit, so I'll have to figure out a way to > > validate when the base/limit informations are valid. > > For a standard bridge, the window change occurs immediately upon > writing the base/limit, so that would be the best time. The standard says a window where limit <= base is invalid/disabled. So the write mechanism from the PCI core should be base = 0xFFFFFFFF limit = true value base = true value In the driver the window should be synchronized after any base/limit update where base < limit. The initial values (ignoring fixed bits) should be base = 0xFFFFFFFF limit = 0 It would be optimal to use the resource framework to ensure the region is available, but that is something for the mbus driver to take care of, not PCI-E... > drivers for A and B. But I think it is possible to do some updates > safely even with the window decoding enabled, without any effect on A > and B, and these are the ones that would cause trouble with your > current scheme. A resize update should just write the true values in any order, the bridge window will expand without interrupting existing traffic. However the core code must ensure that at no time do two bridges decode the same window. That could crash the machine.. Jason -- 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
