[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <031e2b78-7356-013c-9375-5fa0c7deba9e@redhat.com>
Date: Tue, 23 Aug 2022 11:39:30 +0200
From: David Hildenbrand <david@...hat.com>
To: Rebecca Mckeever <remckee0@...il.com>,
Mike Rapoport <rppt@...nel.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 4/8] memblock tests: add additional tests for basic api
and memblock_alloc
On 19.08.22 10:34, Rebecca Mckeever wrote:
> Add tests for memblock_add(), memblock_reserve(), memblock_remove(),
> memblock_free(), and memblock_alloc() for the following test scenarios.
>
> memblock_add() and memblock_reserve():
> - add/reserve a memory block in the gap between two existing memory
> blocks, and check that the blocks are merged into one region
> - try to add/reserve memblock regions that extend past PHYS_ADDR_MAX
>
> memblock_remove() and memblock_free():
> - remove/free a region when it is the only available region
> + These tests ensure that the first region is overwritten with a
> "dummy" region when the last remaining region of that type is
> removed or freed.
> - remove/free() a region that overlaps with two existing regions of the
> relevant type
> - try to remove/free memblock regions that extend past PHYS_ADDR_MAX
>
> memblock_alloc():
> - try to allocate a region that is larger than the total size of available
> memory (memblock.memory)
>
> Signed-off-by: Rebecca Mckeever <remckee0@...il.com>
Reviewed-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists