On Tue, Nov 18, 2008 at 05:59:43PM +0000, Venu Busireddy wrote: > During the resource setup phase, I have noticed that pci_update_resource() > gets called with resno 0 (BAR 0), 6 (PCI_ROM_RESOURCE), 2 (BAR 2), 7 > (VF BAR 0), 9 (VF BAR 2), 11 (VF BAR 4), and 4 (BAR 4), in that order. > > resno 0 (BAR 0) gets bus range 0x80000000-0x807fffff allocated to it. > > resno 6 (PCI_ROM_RESOURCE) gets bus range 0x80800000-0x8087ffff. > > resno 2 (BAR 2) gets bus range 0x80880000-0x80880fff. > > So far so good... > > Now, resno 7 (VF BAR 0) gets bus range 0x80881000-0x88880fff allocated > to it. But when 0x8088100c is written to VF BAR 0, the adpater returns > 0x8080000c. The adapter seems to expect the region to fall on a 8MB > boundary, but the address we assigned falls on a 4K boundary. Could you recompile with CONFIG_PCI_DEBUG=y and send all the resulting messages from dmesg? You may need to increase the size of your CONFIG_LOG_BUF_SHIFT to fit all the extra messages in. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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
