Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-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
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • drivers
  • gpu
  • drm
  • radeon
  • radeon_ring.c
Find file BlameHistoryPermalink
  • Dave Airlie's avatar
    drm/radeon/kms: IB locking dumps out a lockdep ordering issue · ecb114a1
    Dave Airlie authored Sep 15, 2009
    
    
    We sometimes lock IB then the ring and sometimes the ring then
    the IB. This is mostly due to the IB locking not being well defined
    about what data in the structs it actually locks. Define what I
    believe is the correct behaviour and gets rid of the lock dep ordering
    warning.
    Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
    ecb114a1

Replace radeon_ring.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.