> -----Original Message-----
> From: Ali Alnubani <alia...@nvidia.com>
> Sent: Thursday, June 8, 2023 2:43 PM
> To: Li, Miao <miao...@intel.com>; dev@dpdk.org; NBU-Contact-Thomas
> Monjalon (EXTERNAL) <tho...@monjalon.net>
> Cc: sk...@marvell.com; david.march...@redhat.com; ferruh.yi...@amd.com;
> Xia, Chenbo <chenbo....@intel.com>; Cao, Yahui <yahui....@intel.com>;
> Patrick Robb <pr...@iol.unh.edu>
> Subject: RE: [PATCH v4 0/4] Support VFIO sparse mmap in PCI bus
>
> > -----Original Message-----
> > From: Miao Li <miao...@intel.com>
> > Sent: Wednesday, May 31, 2023 8:38 AM
> > To: dev@dpdk.org
> > Cc: sk...@marvell.com; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > <tho...@monjalon.net>; david.march...@redhat.com;
> > ferruh.yi...@amd.com; chenbo....@intel.com; yahui....@intel.com
> > 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
