Re: [PATCH 19/26] mm/numa: Register information into meminspect

Eugen Hristev
2026-01-03T06:37:52Z

On 12/29/25 08:58, Mike Rapoport wrote:
> Hi Eugen,
>
> On Wed, Nov 19, 2025 at 05:44:20PM +0200, Eugen Hristev wrote:
>> Register dynamic information into meminspect:
>> - dynamic node data for each node
>>
>> This information is being allocated for each node, as physical address,
>> so call memblock_mark_inspect that will mark the block accordingly.
>>
>> Signed-off-by: Eugen Hristev <eugen.hristev@linaro.org>
>> ---
>> mm/numa.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/mm/numa.c b/mm/numa.c
>> index 7d5e06fe5bd4..379065dd633e 100644
>> --- a/mm/numa.c
>> +++ b/mm/numa.c
>> @@ -4,6 +4,7 @@
>> #include <linux/printk.h>
>> #include <linux/numa.h>
>> #include <linux/numa_memblks.h>
>> +#include <linux/meminspect.h>
>>
>> struct pglist_data *node_data[MAX_NUMNODES];
>> EXPORT_SYMBOL(node_data);
>> @@ -20,6 +21,7 @@ void __init alloc_node_data(int nid)
>> if (!nd_pa)
>> panic("Cannot allocate %zu bytes for node %d data\n",
>> nd_size, nid);
>> + memblock_mark_inspect(nd_pa, nd_size);
>
> Won't plain meminspect_register_pa() work here?

Yes it would work, but as explained in the other email, it would not go
through memblock API.
We can continue the discussion there

>
>> /* report and initialize */
>> pr_info("NODE_DATA(%d) allocated [mem %#010Lx-%#010Lx]\n", nid,
>> --
>> 2.43.0
>>
>