If you anyway want to simulate VF functionality in PF driver itself, i am not sure why do you need to access VF's config space from PF. FYI, VF's BAR(MMIO) are not used, MMIO regions are carved using VF BARs in PF's SRIOV config space. VFx BAR0 = PF SRIOV BAR0 + BAR_SIZE * x (VF_NUMBER); For accessing VF's MMIO regions you can try mapping PF's pci_dev->resource[PCI_IOV_RESOURCES] and using above formula to get exact MMIO base for corresponding VF. Regards, Sunil. On Wed, Sep 24, 2014 at 10:10 PM, Bob Biloxi <iambobbiloxi@xxxxxxxxx> wrote: > Hi, > > I am new to writing pci sriov drivers. So i could use your help and > expertise here.... > > As I understand once sriov is enabled, the PF driver can access the > PF(Physical Function) configuration space, BAR(MMIO) etc and the VF > driver can access the VF(Virtual Function) configuration space, > BAR(MMIO)... > > Is it possible for a PF driver to access the VF config space, BAR(MMIO)? > If yes, can you please point me as to what needs to be done in order > to do it(existing driver sources will be really helpful). > > Now as to why this requirement is if the PF driver is ready and the VF > driver is still under development, and I want to simulate the VF > functionality from PF itself. > > It would be of immense help to me if anyone can help me understand my > aforementioned query. > > > Thanks a lot!!! > > > Best Regards, > Bob > -- > 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 -- 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
