diff options
| author | Priyanshu Kumar <priyanshukumarpu@gmail.com> | 2026-04-15 12:27:31 +0000 |
|---|---|---|
| committer | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-05-25 20:48:14 +0300 |
| commit | 8623045aa5d24de177c23c86f01d1249ecf2dc10 (patch) | |
| tree | e459e1e9b928f4e9c19eef5f338901ebbd87ddf1 /mm | |
| parent | 502081cb41d1e4e4f76983e950456aa6e1eb9e9b (diff) | |
| download | linux-next-history-8623045aa5d24de177c23c86f01d1249ecf2dc10.tar.gz | |
tools/testing/memblock: fix stale NUMA reservation tests
memblock allocations now reserve memory with MEMBLOCK_RSRV_KERN and,
on NUMA configurations, record the requested node on the reserved
region. Several memblock simulator NUMA tests still expected merges
that only worked before those reservation semantics changed, so the
suite aborted even though the allocator behavior was correct.
Update the NUMA merge expectations in the memblock_alloc_try_nid()
and memblock_alloc_exact_nid_raw() tests to match the current reserved
region metadata rules. For cases that should still merge, create the
pre-existing reservation with matching nid and MEMBLOCK_RSRV_KERN
metadata. Also strengthen the memblock_alloc_node() coverage by
checking the newly created reserved region directly instead of
re-reading the source memory node descriptor.
Finally, drop the stale README/TODO notes that still claimed
memblock_alloc_node() could not be tested.
The memblock simulator passes again with NUMA enabled after these
updates.
Signed-off-by: Priyanshu Kumar <priyanshukumarpu@gmail.com>
Link: https://patch.msgid.link/20260415122731.1768912-1-priyanshukumarpu@gmail.com
[rppt: dropped unrelated changes]
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions
