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
  • iommu
  • amd_iommu.c
Find file BlameHistoryPermalink
  • Joerg Roedel's avatar
    Revert "iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent" · 2d0ec7a1
    Joerg Roedel authored Jun 01, 2015
    This reverts commit 5fc872c7
    
    .
    
    The DMA-API does not strictly require that the memory
    returned by dma_alloc_coherent is zeroed out. For that
    another function (dma_zalloc_coherent) should be used. But
    all other x86 DMA-API implementation I checked zero out the
    memory, so that some drivers rely on it and break when it is
    not.
    
    It seems the (driver-)world is not yet ready for this
    change, so revert it.
    Signed-off-by: default avatarJoerg Roedel <jroedel@suse.de>
    2d0ec7a1

Replace amd_iommu.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.