aboutsummaryrefslogtreecommitdiffstats
path: root/crypto/rmd256.c
diff options
context:
space:
mode:
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2009-05-26 23:33:14 -0400
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2009-05-26 23:33:14 -0400
commit84532a0fc3d5811dca8e3726fe4d372ea87bd7c6 (patch)
treef76d521d22d662dd1dccf22fd42ee57c71446e4f /crypto/rmd256.c
parentcd86a536c81e9300d984327517548ca0652eebf9 (diff)
Revert "powerpc: Rework dma-noncoherent to use generic vmalloc layer"
This reverts commit 33f00dcedb0e22cdb156a23632814fc580fcfcf8. While it was a good idea to try to use the mm/vmalloc.c allocator instead of our own (in fact, ours is itself a dup on an old variant of the vmalloc one), unfortunately, the approach is terminally busted since dma_alloc_coherent() can be called at interrupt time or in atomic contexts and there's little chances we'll make the code in mm/vmalloc.c cope with\ that :-( Until we can get the generic code to forbid that idiocy and fix all drivers abusing it, we pretty much have no choice but revert to our custom virtual space allocator. There's also a problem with SMP safety since freeing such mapping would require an IPI which cannot be done at interrupt time. However, right now, I don't think we support any platform that is both SMP and has non-coherent DMA (don't laugh, I know such things do exist !) so we can sort that out later. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'crypto/rmd256.c')
0 files changed, 0 insertions, 0 deletions