On Thu, Jun 8, 2023 at 3:03 AM David Marchand wrote: > Hello Chenbo, Patrick, > > > On Thu, Jun 8, 2023 at 8:50 AM Xia, Chenbo wrote: > > > > 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? > > Chenbo, > > In theory, this error should have been reported so go ahead and post your > fix. > > Patrick, > > This missing report could be a mail delivery issue (I can see the test > ran at UNH). > I see no trace in test-report ml. > Can you look at the reason? > > Thanks. > > > -- > David Marchand > > I see where the issue is in our reporting process for the windows results and I will resolve it after the CI meeting this morning. Sorry everyone for the oversight. -- Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu