From: shaoqin.huang@intel.com
To: rppt@kernel.org
Cc: Shaoqin Huang <shaoqin.huang@intel.com>,
Karolina Drobnik <karolinadrobnik@gmail.com>,
Rebecca Mckeever <remckee0@gmail.com>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Add tests trying to memblock_add() or memblock_reserve() 129th region
Date: Mon, 22 Aug 2022 10:33:25 +0800 [thread overview]
Message-ID: <20220822023332.127633-1-shaoqin.huang@intel.com> (raw)
From: Shaoqin Huang <shaoqin.huang@intel.com>
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.
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 | 169 +++++++++++++++++++++++
tools/testing/memblock/tests/common.c | 7 +-
tools/testing/memblock/tests/common.h | 3 +
4 files changed, 179 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-22 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 2:33 shaoqin.huang [this message]
2022-08-22 2:33 ` [PATCH 1/3] memblock test: Add test to memblock_add() 129th region shaoqin.huang
2022-08-22 2:33 ` [PATCH 2/3] memblock test: Add test to memblock_reserve() " shaoqin.huang
2022-08-22 2:33 ` [PATCH 3/3] memblock test: Update TODO list shaoqin.huang
2022-08-30 1:49 [PATCH 0/3] Add tests trying to memblock_add() or memblock_reserve() 129th region shaoqin.huang
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=20220822023332.127633-1-shaoqin.huang@intel.com \
--to=shaoqin.huang@intel.com \
--cc=david@redhat.com \
--cc=karolinadrobnik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=remckee0@gmail.com \
--cc=rppt@kernel.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;
as well as URLs for NNTP newsgroup(s).