> -----Original Message----- > From: Ali Alnubani <[email protected]> > Sent: Thursday, June 8, 2023 2:43 PM > To: Li, Miao <[email protected]>; [email protected]; NBU-Contact-Thomas > Monjalon (EXTERNAL) <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; > Xia, Chenbo <[email protected]>; Cao, Yahui <[email protected]>; > Patrick Robb <[email protected]> > Subject: RE: [PATCH v4 0/4] Support VFIO sparse mmap in PCI bus > > > -----Original Message----- > > From: Miao Li <[email protected]> > > Sent: Wednesday, May 31, 2023 8:38 AM > > To: [email protected] > > Cc: [email protected]; NBU-Contact-Thomas Monjalon (EXTERNAL) > > <[email protected]>; [email protected]; > > [email protected]; [email protected]; [email protected] > > Subject: [PATCH v4 0/4] Support VFIO sparse mmap in PCI bus > > > > This series introduces a VFIO standard capability, called sparse > > mmap to PCI bus. In linux kernel, it's defined as > > VFIO_REGION_INFO_CAP_SPARSE_MMAP. Sparse mmap means instead of > > mmap whole BAR region into DPDK process, only mmap part of the > > BAR region after getting sparse mmap information from kernel. > > For the rest of BAR region that is not mmap-ed, DPDK process > > can use pread/pwrite system calls to access. Sparse mmap is > > useful when kernel does not want userspace to mmap whole BAR > > region, or kernel wants to control over access to specific BAR > > region. Vendors can choose to enable this feature or not for > > their devices in their specific kernel modules. > > > > Hello, > > I see the build failure Patrick reported as well and can confirm it's > caused by 095cf6e68b28 ("bus/pci: introduce MMIO read/write"). > Bugzilla ticket: https://bugs.dpdk.org/show_bug.cgi?id=1245
Thanks Ali. I just read the bz and understand what's missing. I will send a patch today. But since last time CI is not reporting the error, this time how could I make sure the fix will perfectly work? Regards, Chenbo > > Regards, > Ali
