summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorHeiko Carstens <hca@linux.ibm.com>2026-09-22 12:41:18 +0200
committerHeiko Carstens <hca@linux.ibm.com>2026-09-22 12:41:18 +0200
commit63753ace73ed68fa5113747a4340925bf870072c (patch)
treeeec6f72ceff2be8e6273fa1ab1784a0a2a595896 /tools/perf/scripts/python/stackcollapse.py
parent1206e6e850c43ec9306a2ec0be04532fd4cf32cb (diff)
parente95e9d86f2be30206a95bd3b8488079231e3e98a (diff)
downloadlinux-63753ace73ed68fa5113747a4340925bf870072c.tar.gz
linux-63753ace73ed68fa5113747a4340925bf870072c.zip
Merge branch 'cio-page-alloc-to-kmalloc'
Mike Rapoport says: ==================== This series covers CIO, QDIO, SCM and IDAL buffer allocations. This is a (small) part of larger work of replacing page allocator calls with kmalloc. My initial intention a few month ago was to remove ugly casts [1], but then willy pointed out that Linus objected to something like this [2] and it looks like more than a decade old technical debt. Largely, anything that doesn't need struct page (or a memdesc in the future) should just use kmalloc() or kvmalloc() to allocate memory. kmalloc() guarantees alignment, physical contiguity and working virt_to_phys() and beside nicer API that returns void * on alloc and doesn't require to know the allocation size on free, kmalloc() provides better debugging capabilities than page allocator. Another thing is that touching these allocation sites gives the reviewers opportunity to see if a PAGE_SIZE buffer is actually needed or maybe another size is appropriate. For larger allocations that don't need physically contiguous memory kvmalloc() can be a better option that __get_free_pages() because under memory pressure it's is easier to allocate several order-0 pages than a physically contiguous chunk with the same number of pages. And last, but not least, removing needless calls to page allocator should help with memdesc (aka project folio) conversion. There will be way less places to audit to see if the user was actually using struct page. The patches are grouped by buffer usage and ordered by file or subsystem. Related CHSC work areas and requests are kept together. While on it, use __free(kfree) for the SCM information buffer and local buffers in synchronous CHSC ioctl handlers. The CHSC cleanup is kept in a separate patch. ==================== Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions