Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • chendotjs
  • linux
  • Repository
  • linux
  • drivers
  • gpu
  • drm
  • amd
  • amdkfd
  • kfd_process.c
Find file BlameHistoryPermalink
  • Felix Kuehling's avatar
    drm/amdkfd: Allow access for mmapping KFD BOs · d4ec4bdc
    Felix Kuehling authored Apr 07, 2021
    
    
    DRM render node file handles are used for CPU mapping of BOs using mmap
    by the Thunk. It uses the DRM render node of the GPU where the BO was
    allocated.
    
    DRM allows mmap access automatically when it creates a GEM handle for a
    BO. KFD BOs don't have GEM handles, so KFD needs to manage access
    manually. Use drm_vma_node_allow to allow user mode to mmap BOs allocated
    with kfd_ioctl_alloc_memory_of_gpu through the DRM render node that was
    used in the kfd_ioctl_acquire_vm call for the same GPU.
    
    Signed-off-by: default avatarFelix Kuehling <Felix.Kuehling@amd.com>
    Acked-by: default avatarChristian König <christian.koenig@amd.com>
    Reviewed-by: default avatarPhilip Yang <philip.yang@amd.com>
    Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
    d4ec4bdc