diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-16 15:03:15 +0300 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2026-09-22 12:40:31 +0200 |
| commit | c76ff72b390b553da029ed79852553e3b917a408 (patch) | |
| tree | 64745c46ba4ea1ae65063faca2bdcc6d362f860f /tools/perf/scripts/python/stackcollapse.py | |
| parent | 91e4448b300a97422f0233d6273649d912c1e741 (diff) | |
| download | linux-c76ff72b390b553da029ed79852553e3b917a408.tar.gz linux-c76ff72b390b553da029ed79852553e3b917a408.zip | |
s390/qdio_main: Use kzalloc() for the IRQ structure
qdio_allocate() allocates the QDIO irq structure.
This memory 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_zeroed_page() with kzalloc() and free_page() with
kfree().
While on it, drop the kmemleak exemption for the CCW. The IRQ structure
is now tracked, so kmemleak can find its pointer to the CCW.
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
