summaryrefslogtreecommitdiffstats
path: root/arch/arm/mm/cache-tauros2.c
diff options
context:
space:
mode:
authorNicolas Pitre <nicolas.pitre@linaro.org>2010-12-16 14:56:34 -0500
committerNicolas Pitre <nico@fluxnic.net>2010-12-19 12:57:16 -0500
commit6d3e6d3640052cac958d61c44597cc216f6ee09f (patch)
treeba246fb50f8d637a0c6074211ddc2e74c4eb1ebe /arch/arm/mm/cache-tauros2.c
parent25cbe45440ea89a3b0f6f7ed326d3d476d53068b (diff)
downloadblackbird-op-linux-6d3e6d3640052cac958d61c44597cc216f6ee09f.tar.gz
blackbird-op-linux-6d3e6d3640052cac958d61c44597cc216f6ee09f.zip
ARM: fix cache-feroceon-l2 after stack based kmap_atomic()
Since commit 3e4d3af501 "mm: stack based kmap_atomic()", it is actively wrong to rely on fixed kmap type indices (namely KM_L2_CACHE) as kmap_atomic() totally ignores them and a concurrent instance of it may happily reuse any slot for any purpose. Because kmap_atomic() is now able to deal with reentrancy, we can get rid of the ad hoc mapping here. While the code is made much simpler, there is a needless cache flush introduced by the usage of __kunmap_atomic(). It is not clear if the performance difference to remove that is worth the cost in code maintenance (I don't think there are that many highmem users on that platform anyway) but that should be reconsidered when/if someone cares enough to do some measurements. Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Diffstat (limited to 'arch/arm/mm/cache-tauros2.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud