| commit | 2d0ec7a19b5796aa958636eeeff072b506460501 | |
| author | Joerg Roedel <jroedel@suse.de> | |
| Mon, 1 Jun 2015 15:30:57 +0000 (1 17:30 +0200) | ||
| committer | Joerg Roedel <jroedel@suse.de> | |
| Tue, 2 Jun 2015 06:46:32 +0000 (2 08:46 +0200) | ||
| tree | f2b9357156dd8332baadb9f10db5e455af7787c7 | treesnapshot (tar.gz zip) |
| parent | c65b99f046843d2455aa231747b5a07a999a9f3d | commitdiff |
Revert "iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent"
This reverts commit 5fc872c7323534e8f7dc21bab635e7a9b9659e07.
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: Joerg Roedel <jroedel@suse.de>
This reverts commit 5fc872c7323534e8f7dc21bab635e7a9b9659e07.
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: Joerg Roedel <jroedel@suse.de>
| drivers/iommu/amd_iommu.c | diffblobblamehistory |