diff options
| author | Mike Rapoport <[email protected]> | 2021-11-05 20:43:07 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2021-11-06 20:30:40 +0000 |
| commit | 5787ea5bed7607cbee26da492e574f94975e4d76 (patch) | |
| tree | 960288b8dbcb5d587a4def610bd6baf9a43509f0 /mm/sparse.c | |
| parent | tools/vm/page-types.c: print file offset in hexadecimal (diff) | |
| download | kernel-5787ea5bed7607cbee26da492e574f94975e4d76.tar.gz kernel-5787ea5bed7607cbee26da492e574f94975e4d76.zip | |
arch_numa: simplify numa_distance allocation
Patch series "memblock: cleanup memblock_free interface", v2.
This is the fix for memblock freeing APIs mismatch [1].
The first patch is a cleanup of numa_distance allocation in arch_numa
I've spotted during the conversion. The second patch is a fix for Xen
memory freeing on some of the error paths.
[1] https://lore.kernel.org/all/CAHk-=wj9k4LZTz+svCxLYs5Y1=+yKrbAUArH1+ghyG3OLd8VVg@mail.gmail.com
This patch (of 6):
Memory allocation of numa_distance uses memblock_phys_alloc_range()
without actual range limits, converts the returned physical address to
virtual and then only uses the virtual address for further
initialization.
Simplify this by replacing memblock_phys_alloc_range() with
memblock_alloc().
Link: https://lkml.kernel.org/r/[email protected]
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Mike Rapoport <[email protected]>
Cc: Christophe Leroy <[email protected]>
Cc: Juergen Gross <[email protected]>
Cc: Shahab Vahedi <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'mm/sparse.c')
0 files changed, 0 insertions, 0 deletions