Bjorn, To be honest, the output above is picked up from other guy's mail, because I composed the patch mail at home and left the real bug material at company, they 'really' hit an issue confused by lspci output while SR-IOV is initialized to disabled . There is an error in above output as description that not made on purpose, sorry again, the IOVCtl: Enable+ should be IOVCtl: Enable-
Current iov.c code, in fact, initializing the SR-IOV to disabled whatever BIOS setup the PCI_SRIOV_XX registers. Thanks, Ethan On Wed, Nov 20, 2013 at 8:07 AM, Bjorn Helgaas <bhelg...@google.com> wrote: > On Tue, Nov 19, 2013 at 3:24 PM, Bjorn Helgaas <bhelg...@google.com> wrote: >> [+cc linux-pci] >> >> On Wed, Nov 6, 2013 at 7:49 AM, ethan.zhao <ethan.ker...@gmail.com> wrote: >>> Though no specification about NumVFs register initial value after POST, to >>> void the confusion >>> lspci output as following before VF was enabled, we should clear the NumVFs >>> value left by BIOS >>> to zero: >>> >>> $lspci -vvv -s 03:00.0 >>> Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network >>> Connection (rev 01) >>> ~ >>> Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV) >>> IOVCap: Migration-, Interrupt Message Number: 000 >>> IOVCtl: Enable+ Migration- Interrupt- MSE+ ARIHierarchy+ >>> IOVSta: Migration- >>> Initial VFs: 64, Total VFs: 64, Number of VFs: 64, Function >>> Dependency Link: 00 >>> ^dazed ! > > Did you mean to show lspci output from before SR-IOV was enabled? It > looks like SR-IOV is enabled here, so I don't think your patch would > change this output at all. > > Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/