All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: shaoqin.huang@intel.com
Cc: David Hildenbrand <david@redhat.com>,
	Karolina Drobnik <karolinadrobnik@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Rebecca Mckeever <remckee0@gmail.com>
Subject: Re: [PATCH v4 0/3] Add tests trying to memblock_add() or memblock_reserve() 129th region
Date: Mon, 24 Oct 2022 18:37:38 +0300	[thread overview]
Message-ID: <Y1axQhbZlZ3lXion@kernel.org> (raw)
In-Reply-To: <20221011062128.49359-1-shaoqin.huang@intel.com>

On Tue, Oct 11, 2022 at 02:21:19PM +0800, shaoqin.huang@intel.com wrote:
> 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.
> 
> 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(-)

Applied, thanks!

-- 
Sincerely yours,
Mike.

  parent reply	other threads:[~2022-10-24 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  6:21 [PATCH v4 0/3] Add tests trying to memblock_add() or memblock_reserve() 129th region shaoqin.huang
2022-10-11  6:21 ` [PATCH v4 1/3] memblock test: Add test to memblock_add() " shaoqin.huang
2022-10-11  6:21 ` [PATCH v4 2/3] memblock test: Add test to memblock_reserve() " shaoqin.huang
2022-10-24 15:36   ` Mike Rapoport
2022-10-11  6:21 ` [PATCH v4 3/3] memblock test: Update TODO list shaoqin.huang
2022-10-24 15:37 ` Mike Rapoport [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-19  2:47 [PATCH v4 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=Y1axQhbZlZ3lXion@kernel.org \
    --to=rppt@kernel.org \
    --cc=david@redhat.com \
    --cc=karolinadrobnik@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=remckee0@gmail.com \
    --cc=shaoqin.huang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.