> Yes. This patch should also be divided in 4 parts :
>
>  - kernel header changes with links to the threads modifying the kernel.
>   - common part,
>   - vpda part,
>   - and vfio,

ok, I will divide it into 4 patches.
thanks Cédric

On Fri, Jan 17, 2025 at 2:15 AM Cédric Le Goater <c...@redhat.com> wrote:

> >> --- a/linux-headers/linux/vfio.h
> >> +++ b/linux-headers/linux/vfio.h
> >> @@ -1560,6 +1560,7 @@ struct vfio_iommu_type1_dma_map {
> >>   #define VFIO_DMA_MAP_FLAG_READ (1 << 0)            /* readable from
> device */
> >>   #define VFIO_DMA_MAP_FLAG_WRITE (1 << 1)   /* writable from device */
> >>   #define VFIO_DMA_MAP_FLAG_VADDR (1 << 2)
> >> +#define VFIO_DMA_MAP_FLAG_MMIO (1 << 3)
> >
> > Where's the kernel patch that implements the MMIO map flag.  That needs
> > to come first.
>
> Yes. This patch should also be divided in 4 parts :
>
>    - kernel header changes with links to the threads modifying the kernel.
>    - common part,
>    - vpda part,
>    - and vfio,
>
>
> Thanks,
>
> C.
>
>
>
> > I also don't understand why we're creating multiple read-only and
> > ramdev flags to distill back into vfio mapping flags.  Thanks,
> >
>
>

Reply via email to