[v4,0/3] Add tests trying to memblock_add() or memblock_reserve() 129th region

Message

Huang, Shaoqin Sept. 19, 2022, 2:47 a.m. UTC

From: Shaoqin Huang <[e-mail]>

These tests is aimed for testing the memblock_double_array() can work normal. It
will using the dummy_physical_memory_init() to add the valid memory region into
the memblock.memory, and this memory region will be choosed when
memblock_double_array() to allocate the new memory region to double the regions.
Thus the new memory.regions or reserved.regions will occupy the valid memory
region, and the memory.max and reserved.max also being doubled. Check all of
these changed stuff, to make sure it actually success.

Changelog:
----------
v4:
  - Increase the MEM_SIZE to SZ_32K. And makes the calculation process in
  memblock_add_many_check() more simpler.
v3:
  - Avoid to allocated multiple memory region from dummy_physical_memory_base(),
  split the memory into different part instead.
  - Some comments improvement.
v2:
  - Modify the get_memory_block_base() to dummy_physical_memory_base().
  - memory_add() the memory which is allocated from dummy_physical_memory_init()
  instead of some faked memory.
  - Add more comments to illustrate the test process.
  - Add a function dummy_physical_memory_cleanup_many() to free multiple memory
  which is allocated from dummy_physical_memory_init().

Shaoqin Huang (3):
  memblock test: Add test to memblock_add() 129th region
  memblock test: Add test to memblock_reserve() 129th region
  memblock test: Update TODO list

 tools/testing/memblock/TODO              |  11 +-
 tools/testing/memblock/tests/basic_api.c | 184 +++++++++++++++++++++++
 tools/testing/memblock/tests/common.c    |   7 +-
 tools/testing/memblock/tests/common.h    |   6 +-
 4 files changed, 196 insertions(+), 12 deletions(-)