Hi Thomas, As long as pmd or application doesn't access dev->mem_resource[i].addr, secondary process works with igb_uio. But for pci devices like crypto_qat, pmd checks for dev->mem_resource[i].addr and bails out if the address is null.
Root cause is, not initializing the mapped address in rte_pcidev when device is exposed through igb_uio. Thanks, Vijay On Mon, 30 Mar 2020 at 18:54, Thomas Monjalon <tho...@monjalon.net> wrote: > > 06/03/2020 13:28, Ferruh Yigit: > > On 3/6/2020 12:02 AM, Vijaya Mohan Guvva wrote: > > > For pci devices presented through igb_uio, pcidev->mem_resource[] is > > > not populated when the device is initialized for secondary process. > > > > > > Initialize pcidev->mem_resource[] with pci-bar mapped addresses. > > > > > > Signed-off-by: Vijaya Mohan Guvva <vijay1...@gmail.com> > > > > Reviewed-by: Ferruh Yigit <ferruh.yi...@intel.com> > > Do you mean secondary process never worked with igb_uio? > Or is there a specific case? > What is the root cause? > Should it be backported to stable? > >
