diff options
author | Shaoqin Huang <shaoqin.huang@intel.com> | 2022-10-11 09:21:20 +0300 |
---|---|---|
committer | Mike Rapoport <rppt@linux.ibm.com> | 2022-10-31 11:15:00 +0300 |
commit | 085bdaa6eb1476ec054164bdc4001bc3916ff5cb (patch) | |
tree | cd8e197921ba412b48332db6d418818446ba8015 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 30a0b95b1335e12efef89dd78518ed3e4a71a763 (diff) | |
download | linux-085bdaa6eb1476ec054164bdc4001bc3916ff5cb.tar.xz |
memblock test: Add test to memblock_add() 129th region
Add 129th region into the memblock, and this will trigger the
memblock_double_array() function, this needs valid memory regions. So
using dummy_physical_memory_init() to allocate a large enough memory
region, and split it into a large enough memory which can be choosed by
memblock_double_array(), and the left memory will be split into small
memory region, and add them into the memblock. It make sure the
memblock_double_array() will always choose the valid memory region that
is allocated by the dummy_physical_memory_init().
So memblock_double_array() must success.
Another thing should be done is to restore the memory.regions after
memblock_double_array(), due to now the memory.regions is pointing to a
memory region allocated by dummy_physical_memory_init(). And it will
affect the subsequent tests if we don't restore the memory region. So
simply record the origin region, and restore it after the test.
Signed-off-by: Shaoqin Huang <shaoqin.huang@intel.com>
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Link: https://lore.kernel.org/r/20221011062128.49359-2-shaoqin.huang@intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions