lkml.org 
[lkml]   [2019]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 17/25] nouveau: use alloc_page_vma directly
    Date
    hmm_vma_alloc_locked_page is scheduled to go away, use the proper
    mm function directly.

    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Jason Gunthorpe <jgg@mellanox.com>
    ---
    drivers/gpu/drm/nouveau/nouveau_dmem.c | 3 ++-
    1 file changed, 2 insertions(+), 1 deletion(-)

    diff --git a/drivers/gpu/drm/nouveau/nouveau_dmem.c b/drivers/gpu/drm/nouveau/nouveau_dmem.c
    index 40c47d6a7d78..a50f6fd2fe24 100644
    --- a/drivers/gpu/drm/nouveau/nouveau_dmem.c
    +++ b/drivers/gpu/drm/nouveau/nouveau_dmem.c
    @@ -148,11 +148,12 @@ nouveau_dmem_fault_alloc_and_copy(struct vm_area_struct *vma,
    if (!spage || !(src_pfns[i] & MIGRATE_PFN_MIGRATE))
    continue;

    - dpage = hmm_vma_alloc_locked_page(vma, addr);
    + dpage = alloc_page_vma(GFP_HIGHUSER, vma, addr);
    if (!dpage) {
    dst_pfns[i] = MIGRATE_PFN_ERROR;
    continue;
    }
    + lock_page(dpage);

    dst_pfns[i] = migrate_pfn(page_to_pfn(dpage)) |
    MIGRATE_PFN_LOCKED;
    --
    2.20.1
    \
     
     \ /
      Last update: 2019-06-17 14:29    [W:4.246 / U:0.196 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site