From: Mike Rapoport <rppt@kernel.org>
To: Tianyi Chen <hi@tychen.cc>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] memblock tests: cover low-address allocations
Date: Wed, 9 Sep 2026 20:31:37 +0300 [thread overview]
Message-ID: <aqGX-ZhxsJppfNpi@kernel.org> (raw)
In-Reply-To: <178874362959.1415955.18132997964995947947.memblock-v2-0@tychen.cc>
Hi,
For the future postings, please don't send vN+1 as a reply to vN.
On Mon, Sep 07, 2026 at 09:20:31AM +0800, Tianyi Chen wrote:
> Model a low allocation limit within the dummy memory registered with
> memblock, then exercise memblock_alloc_low() in both allocation directions.
>
> Changes in v2, following Mike Rapoport's review:
> - Clarify why the limit splits MEM_SIZE, the region registered by
> setup_memblock(), rather than the larger PHYS_MEM_SIZE malloc buffer.
> - Explain why the malloc-backed base still needs alignment.
> - Describe the boundary in terms of the last usable byte and clarify
> that reserving low memory succeeds; the following allocation fails.
> - Update Assisted-by tags to the required tool:model format.
>
> No allocator or test behavior changes from v1.
>
> Validation with the existing Makefile and ASan/UBSan enabled:
> - Default, NUMA=1, 32BIT_PHYS_ADDR_T=1, 32BIT_PHYS_ADDR_T=1 with NUMA=1,
> and MEMBLOCK_DEBUG=1 with NUMA=1 builds passed.
> - Each configuration passed both ./main -v and ./main -v -m.
> - A separate BUILD=32 run still hits the pre-existing
> memblock_free_near_max_check assertion in basic_api.c, also seen on
> the baseline. This is distinct from the passing 32-bit physical-address
> configuration above.
>
> v1: https://lore.kernel.org/r/20260906144011.848898-1-hi@tychen.cc
> Review: https://lore.kernel.org/r/ap3LTQlKTpDbAEJZ@kernel.org
> Review: https://lore.kernel.org/r/ap3NJsaG10rLDVpd@kernel.org
>
> Tianyi Chen (2):
> memblock tests: model the low allocation limit within dummy memory
> memblock tests: cover allocations below the low address limit
>
> tools/testing/memblock/Makefile | 3 +-
> tools/testing/memblock/README | 14 +-
> tools/testing/memblock/TODO | 5 -
> tools/testing/memblock/asm/dma.h | 6 +
> tools/testing/memblock/main.c | 2 +
> tools/testing/memblock/tests/alloc_low_api.c | 148 +++++++++++++++++++
> tools/testing/memblock/tests/alloc_low_api.h | 9 ++
> tools/testing/memblock/tests/common.c | 6 +
> 8 files changed, 180 insertions(+), 13 deletions(-)
> delete mode 100644 tools/testing/memblock/TODO
> create mode 100644 tools/testing/memblock/tests/alloc_low_api.c
> create mode 100644 tools/testing/memblock/tests/alloc_low_api.h
>
> --
> 2.55.0
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-09-09 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 14:40 [PATCH 1/2] memblock tests: model the low allocation limit within dummy memory Tianyi Chen
2026-09-06 14:40 ` [PATCH 2/2] memblock tests: cover allocations below the low address limit Tianyi Chen
2026-09-06 20:29 ` Mike Rapoport
2026-09-06 20:21 ` [PATCH 1/2] memblock tests: model the low allocation limit within dummy memory Mike Rapoport
2026-09-07 1:20 ` Tianyi Chen
2026-09-07 1:20 ` [PATCH v2 0/2] memblock tests: cover low-address allocations Tianyi Chen
2026-09-07 1:20 ` [PATCH v2 1/2] memblock tests: model the low allocation limit within dummy memory Tianyi Chen
2026-09-09 17:14 ` Mike Rapoport
2026-09-07 1:20 ` [PATCH v2 2/2] memblock tests: cover allocations below the low address limit Tianyi Chen
2026-09-09 17:14 ` Mike Rapoport
2026-09-09 17:31 ` Mike Rapoport [this message]
2026-09-09 23:55 ` [PATCH v2 0/2] memblock tests: cover low-address allocations Tianyi Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aqGX-ZhxsJppfNpi@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hi@tychen.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox