Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM()... | linux-arm-kernel

[PATCH v3 00/26] mm: introduce numa_memblks · Mike Rapoport <rppt@kernel.org> · 2024-08-01
[PATCH v3 01/26] mm: move kernel/numa.c to mm/ · Mike Rapoport <rppt@kernel.org> · 2024-08-01
[PATCH v3 02/26] MIPS: sgi-ip27: make NODE_DATA() the same as on all other architectures · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 02/26] MIPS: sgi-ip27: make NODE_DATA() the same as on all other architectures · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-01
Re: [PATCH v3 02/26] MIPS: sgi-ip27: make NODE_DATA() the same as on all other architectures · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 03/26] MIPS: sgi-ip27: ensure node_possible_map only contains valid nodes · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 03/26] MIPS: sgi-ip27: ensure node_possible_map only contains valid nodes · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-01
Re: [PATCH v3 03/26] MIPS: sgi-ip27: ensure node_possible_map only contains valid nodes · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 04/26] MIPS: sgi-ip27: drop HAVE_ARCH_NODEDATA_EXTENSION · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 04/26] MIPS: sgi-ip27: drop HAVE_ARCH_NODEDATA_EXTENSION · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-01
Re: [PATCH v3 04/26] MIPS: sgi-ip27: drop HAVE_ARCH_NODEDATA_EXTENSION · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 05/26] MIPS: loongson64: rename __node_data to node_data · Mike Rapoport <rppt@kernel.org> · 2024-08-01
[PATCH v3 06/26] MIPS: loongson64: drop HAVE_ARCH_NODEDATA_EXTENSION · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 06/26] MIPS: loongson64: drop HAVE_ARCH_NODEDATA_EXTENSION · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-01
Re: [PATCH v3 06/26] MIPS: loongson64: drop HAVE_ARCH_NODEDATA_EXTENSION · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Andrew Morton <akpm@linux-foundation.org> · 2024-08-03
Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Mike Rapoport <rppt@kernel.org> · 2024-08-04
Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-04
Re: [PATCH v3 07/26] mm: drop CONFIG_HAVE_ARCH_NODEDATA_EXTENSION · Mike Rapoport <rppt@kernel.org> · 2024-08-05
[PATCH v3 08/26] arch, mm: move definition of node_data to generic code · Mike Rapoport <rppt@kernel.org> · 2024-08-01
[PATCH v3 09/26] arch, mm: pull out allocation of NODE_DATA to generic code · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 09/26] arch, mm: pull out allocation of NODE_DATA to generic code · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 09/26] arch, mm: pull out allocation of NODE_DATA to generic code · Mike Rapoport <rppt@kernel.org> · 2024-08-05
[PATCH v3 10/26] x86/numa: simplify numa_distance allocation · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 10/26] x86/numa: simplify numa_distance allocation · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 10/26] x86/numa: simplify numa_distance allocation · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory · Dan Williams <hidden> · 2024-08-05
Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory · Mike Rapoport <rppt@kernel.org> · 2024-08-05
Re: [PATCH v3 11/26] x86/numa: use get_pfn_range_for_nid to verify that node spans memory · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 12/26] x86/numa: move FAKE_NODE_* defines to numa_emu · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 12/26] x86/numa: move FAKE_NODE_* defines to numa_emu · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 13/26] x86/numa_emu: simplify allocation of phys_dist · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 13/26] x86/numa_emu: simplify allocation of phys_dist · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 14/26] x86/numa_emu: split __apicid_to_node update to a helper function · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 14/26] x86/numa_emu: split __apicid_to_node update to a helper function · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 15/26] x86/numa_emu: use a helper function to get MAX_DMA32_PFN · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 15/26] x86/numa_emu: use a helper function to get MAX_DMA32_PFN · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 16/26] x86/numa: numa_{add,remove}_cpu: make cpu parameter unsigned · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 16/26] x86/numa: numa_{add,remove}_cpu: make cpu parameter unsigned · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 17/26] mm: introduce numa_memblks · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 17/26] mm: introduce numa_memblks · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 17/26] mm: introduce numa_memblks · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 18/26] mm: move numa_distance and related code from x86 to numa_memblks · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 18/26] mm: move numa_distance and related code from x86 to numa_memblks · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 18/26] mm: move numa_distance and related code from x86 to numa_memblks · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 19/26] mm: introduce numa_emulation · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 19/26] mm: introduce numa_emulation · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 19/26] mm: introduce numa_emulation · Dan Williams <hidden> · 2024-08-05
Re: [PATCH v3 19/26] mm: introduce numa_emulation · David Hildenbrand <hidden> · 2024-08-06
Re: [PATCH v3 19/26] mm: introduce numa_emulation · David Hildenbrand <hidden> · 2024-08-06
Re: [PATCH v3 19/26] mm: introduce numa_emulation · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 20/26] mm: numa_memblks: introduce numa_memblks_init · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 20/26] mm: numa_memblks: introduce numa_memblks_init · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 20/26] mm: numa_memblks: introduce numa_memblks_init · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 21/26] mm: numa_memblks: make several functions and variables static · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 21/26] mm: numa_memblks: make several functions and variables static · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 21/26] mm: numa_memblks: make several functions and variables static · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo · Dan Williams <hidden> · 2024-08-05
Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo · Mike Rapoport <rppt@kernel.org> · 2024-08-05
Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 23/26] of, numa: return -EINVAL when no numa-node-id is found · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 23/26] of, numa: return -EINVAL when no numa-node-id is found · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 23/26] of, numa: return -EINVAL when no numa-node-id is found · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 24/26] arch_numa: switch over to numa_memblks · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 24/26] arch_numa: switch over to numa_memblks · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 24/26] arch_numa: switch over to numa_memblks · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 25/26] mm: make range-to-target_node lookup facility a part of numa_memblks · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 25/26] mm: make range-to-target_node lookup facility a part of numa_memblks · Dan Williams <hidden> · 2024-08-05
Re: [PATCH v3 25/26] mm: make range-to-target_node lookup facility a part of numa_memblks · David Hildenbrand <hidden> · 2024-08-06
[PATCH v3 26/26] docs: move numa=fake description to kernel-parameters.txt · Mike Rapoport <rppt@kernel.org> · 2024-08-01
Re: [PATCH v3 26/26] docs: move numa=fake description to kernel-parameters.txt · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 26/26] docs: move numa=fake description to kernel-parameters.txt · David Hildenbrand <hidden> · 2024-08-06
Re: [PATCH v3 00/26] mm: introduce numa_memblks · Jonathan Cameron <Jonathan.Cameron@Huawei.com> · 2024-08-02
Re: [PATCH v3 00/26] mm: introduce numa_memblks · Dan Williams <hidden> · 2024-08-05

Re: [PATCH v3 22/26] mm: numa_memblks: use memblock_{start,end}_of_DRAM() when sanitizing meminfo

From: Dan Williams <hidden>
Date: 2024-08-05 20:21:11
Also in: linux-acpi, linux-arch, linux-cxl, linux-devicetree, linux-doc, linux-mips, linux-mm, linux-riscv, linux-s390, linux-sh, linuxppc-dev, lkml, loongarch, nvdimm, sparclinux

Mike Rapoport wrote:

From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>

numa_cleanup_meminfo() moves blocks outside system RAM to
numa_reserved_meminfo and it uses 0 and PFN_PHYS(max_pfn) to determine
the memory boundaries.

Replace the memory range boundaries with more portable
memblock_start_of_DRAM() and memblock_end_of_DRAM().

Can you say a bit more about why this is more portable? Is there any
scenario for which (0, max_pfn) does the wrong thing?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help