From: Mike Rapoport <rppt@kernel.org>
To: Rebecca Mckeever <remckee0@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v3 0/8] memblock tests: update and extend memblock simulator
Date: Tue, 30 Aug 2022 13:13:18 +0300 [thread overview]
Message-ID: <Yw3ivnYL4urhRlCQ@kernel.org> (raw)
In-Reply-To: <cover.1661578349.git.remckee0@gmail.com>
On Sat, Aug 27, 2022 at 12:42:42AM -0500, Rebecca Mckeever wrote:
> These patches update existing tests in memblock simulator, add
> additional tests for memblock functions that are already being tested,
> and add test coverage for additional memblock functions.
>
> Rebecca Mckeever (8):
> memblock tests: update tests to check if memblock_alloc zeroed memory
> memblock tests: update zeroed memory check for memblock_alloc_* tests
> memblock tests: add labels to verbose output for generic alloc tests
> memblock tests: add additional tests for basic api and memblock_alloc
> memblock tests: update alloc_api to test memblock_alloc_raw
> memblock tests: update alloc_nid_api to test
> memblock_alloc_try_nid_raw
> memblock tests: add tests for memblock_*bottom_up functions
> memblock tests: add tests for memblock_trim_memory
>
> tools/testing/memblock/tests/alloc_api.c | 168 +++-
> .../memblock/tests/alloc_helpers_api.c | 20 +-
> tools/testing/memblock/tests/alloc_nid_api.c | 252 +++---
> tools/testing/memblock/tests/basic_api.c | 767 ++++++++++++++++++
> tools/testing/memblock/tests/common.c | 7 +
> tools/testing/memblock/tests/common.h | 55 ++
> 6 files changed, 1082 insertions(+), 187 deletions(-)
Applied, thanks!
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2022-08-30 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 5:42 Rebecca Mckeever
2022-08-27 5:42 ` [PATCH v3 3/8] memblock tests: add labels to verbose output for generic alloc tests Rebecca Mckeever
2022-08-28 2:45 ` [PATCH v3 0/8] memblock tests: update and extend memblock simulator Huang, Shaoqin
2022-08-30 10:13 ` Mike Rapoport [this message]
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=Yw3ivnYL4urhRlCQ@kernel.org \
--to=rppt@kernel.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=remckee0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox