diff options
author | Thomas Gleixner <[email protected]> | 2020-11-03 10:27:19 +0100 |
---|---|---|
committer | Thomas Gleixner <[email protected]> | 2020-11-06 23:14:55 +0100 |
commit | 389755c250814185938f5b04334a4f0184c30647 (patch) | |
tree | 3ce03d2f790b6a77c87398c161329341ee5e8ca5 /tools/perf/scripts/python/stackcollapse.py | |
parent | 298fa1ad5571f59cb3ca5497a9455f36867f065e (diff) |
highmem: Make DEBUG_HIGHMEM functional
For some obscure reason when CONFIG_DEBUG_HIGHMEM is enabled the stack
depth is increased from 20 to 41. But the only thing DEBUG_HIGHMEM does is
to enable a few BUG_ON()'s in the mapping code.
That's a leftover from the historical mapping code which had fixed entries
for various purposes. DEBUG_HIGHMEM inserted guard mappings between the map
types. But that got all ditched when kmap_atomic() switched to a stack
based map management. Though the WITH_KM_FENCE magic survived without being
functional. All the thing does today is to increase the stack depth.
Add a working implementation to the generic kmap_local* implementation.
Signed-off-by: Thomas Gleixner <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Christoph Hellwig <[email protected]>
Cc: Andrew Morton <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions