On 11/21/18 2:56 PM, Souptick Joarder wrote: > On Thu, Nov 22, 2018 at 1:08 AM Boris Ostrovsky > <boris.ostrovsky@xxxxxxxxxx> wrote: >> On 11/21/18 1:24 AM, Souptick Joarder wrote: >>> On Thu, Nov 15, 2018 at 9:09 PM Souptick Joarder <jrdr.linux@xxxxxxxxx> wrote: >>>> Previouly drivers have their own way of mapping range of >>>> kernel pages/memory into user vma and this was done by >>>> invoking vm_insert_page() within a loop. >>>> >>>> As this pattern is common across different drivers, it can >>>> be generalized by creating a new function and use it across >>>> the drivers. >>>> >>>> vm_insert_range is the new API which will be used to map a >>>> range of kernel memory/pages to user vma. >>>> >>>> All the applicable places are converted to use new vm_insert_range >>>> in this patch series. >>>> >>>> Souptick Joarder (9): >>>> mm: Introduce new vm_insert_range API >>>> arch/arm/mm/dma-mapping.c: Convert to use vm_insert_range >>>> drivers/firewire/core-iso.c: Convert to use vm_insert_range >>>> drm/rockchip/rockchip_drm_gem.c: Convert to use vm_insert_range >>>> drm/xen/xen_drm_front_gem.c: Convert to use vm_insert_range >>>> iommu/dma-iommu.c: Convert to use vm_insert_range >>>> videobuf2/videobuf2-dma-sg.c: Convert to use vm_insert_range >>>> xen/gntdev.c: Convert to use vm_insert_range >>>> xen/privcmd-buf.c: Convert to use vm_insert_range >>> Any further comment on driver changes ? >> Xen drivers (the last two patches) look fine to me. > Thanks, can I considered this as Reviewed-by ? Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
