lkml.org 
[lkml]   [2020]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[RFC 15/17] drm: xen: fix sg_table nents vs. orig_nents misuse
    Date
    The Documentation/DMA-API-HOWTO.txt states that dma_map_sg returns the
    numer of the created entries in the DMA address space. However the
    subsequent calls to dma_sync_sg_for_{device,cpu} and dma_unmap_sg must be
    called with the original number of entries passed to dma_map_sg. The
    sg_table->nents in turn holds the result of the dma_map_sg call as stated
    in include/linux/scatterlist.h. Adapt the code to obey those rules.

    Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
    ---
    drivers/gpu/drm/xen/xen_drm_front_gem.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/drivers/gpu/drm/xen/xen_drm_front_gem.c b/drivers/gpu/drm/xen/xen_drm_front_gem.c
    index f0b85e0..ba4bdc5 100644
    --- a/drivers/gpu/drm/xen/xen_drm_front_gem.c
    +++ b/drivers/gpu/drm/xen/xen_drm_front_gem.c
    @@ -215,7 +215,7 @@ struct drm_gem_object *
    return ERR_PTR(ret);

    DRM_DEBUG("Imported buffer of size %zu with nents %u\n",
    - size, sgt->nents);
    + size, sgt->orig_nents);

    return &xen_obj->base;
    }
    --
    1.9.1
    \
     
     \ /
      Last update: 2020-04-28 15:20    [W:4.184 / U:0.240 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site