Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • 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
Switch branch/tag
  • linux
  • drivers
  • gpu
  • drm
  • amd
  • amdgpu
  • mxgpu_nv.c
Find file BlameHistoryPermalink
  • Jingwen Chen's avatar
    drm/amdgpu: SRIOV flr_work should take write_lock · 798c5115
    Jingwen Chen authored Jul 01, 2021
    
    
    [Why]
    If flr_work takes read_lock, then other threads who takes
    read_lock can access hardware when host is doing vf flr.
    
    [How]
    flr_work should take write_lock to avoid this case.
    
    Signed-off-by: default avatarJingwen Chen <Jingwen.Chen2@amd.com>
    Reviewed-by: default avatarMonk Liu <monk.liu@amd.com>
    Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
    798c5115