arch_numa-simplify-numa_distance-allocation.patch removed from -mm tree
The patch titled
Subject: arch_numa: simplify numa_distance allocation
has been removed from the -mm tree. Its filename was
arch_numa-simplify-numa_distance-allocation.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Mike Rapoport <[email protected]>
Subject: 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().
---
drivers/base/arch_numa.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/base/arch_numa.c renamed from drivers/base/arch_numa.c~arch_numa-simplify-numa_distance-allocation +2 -4
@@ -337,15 +337,13 @@ void __init numa_free_distance(void)static int __init numa_alloc_distance (void ) {size_t size; -u64 phys;int i, j; size = nr_node_ids * nr_node_ids *sizeof (numa_distance[0 ]); - phys =memblock_phys_alloc_range (size,PAGE_SIZE ,0 ,PFN_PHYS (max_pfn)); -if (WARN_ON (!phys)) + numa_distance =memblock_alloc (size,PAGE_SIZE ); +if (WARN_ON (!numa_distance))return -ENOMEM ; - numa_distance =__va (phys); numa_distance_cnt = nr_node_ids;/* fill with the default distances */
_
Patches currently in -mm which might be from [email protected] are