diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-16 15:03:20 +0300 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2026-09-22 12:40:32 +0200 |
| commit | e95e9d86f2be30206a95bd3b8488079231e3e98a (patch) | |
| tree | eec6f72ceff2be8e6273fa1ab1784a0a2a595896 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 4380decdce1f8bed35b0d4b7b23c574f95c528b5 (diff) | |
| download | linux-e95e9d86f2be30206a95bd3b8488079231e3e98a.tar.gz linux-e95e9d86f2be30206a95bd3b8488079231e3e98a.zip | |
s390/scm: Use kmalloc() for SCM information
scm_update_information() allocates the response buffer for the CHSC
Store SCM Information command.
This buffer can be allocated with kmalloc() as there's nothing special
about it to go directly to the page allocator.
kmalloc() provides a better API that does not require ugly casts and
kfree() does not need to know the size of the freed object.
Performance difference between kmalloc() and __get_free_pages() is not
measurable as both allocators take an object/page from a per-CPU list for
fast path allocations.
For the slow path the performance is anyway determined by the amount of
reclaim involved rather than by what allocator is used.
Replace use of __get_free_page() with kmalloc() and free_page() with
kfree().
While on it, use __free(kfree) for the local response buffer.
Link: https://lore.kernel.org/all/635405e4-9423-4a25-a6e7-e03c8ea0bcbe@redhat.com
Assisted-by: copilot:claude-opus
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
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
