From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Rebecca Mckeever <remckee0@gmail.com>,
Shaoqin Huang <shaoqin.huang@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock updates for v6.1
Date: Tue, 11 Oct 2022 13:37:49 +0300 [thread overview]
Message-ID: <Y0VHfYkFUqYwVAru@kernel.org> (raw)
Hi Linus,
The following changes since commit b90cb1053190353cc30f0fef0ef1f378ccc063c5:
Linux 6.0-rc3 (2022-08-28 15:05:29 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock for-next
for you to fetch changes up to 3e4519b7afc2f9d99f9303468ee0b23f88399c8d:
memblock tests: add generic NUMA tests for memblock_alloc_try_nid* (2022-09-18 10:30:20 +0300)
----------------------------------------------------------------
memblock: test suite improvements
* Added verification that memblock allocations zero the allocated memory
* Added more test cases for memblock_add(), memblock_remove(),
memblock_reserve() and memblock_free()
* Added tests for memblock_*_raw() family
* Added tests for NUMA-aware allocations in memblock_alloc_try_nid() and
memblock_alloc_try_nid_raw()
----------------------------------------------------------------
Rebecca Mckeever (16):
memblock tests: add command line help option
memblock tests: update reference to obsolete build option in comments
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
memblock tests: remove 'cleared' from comment blocks
memblock_tests: move variable declarations to single block
memblock tests: add simulation of physical memory with multiple NUMA nodes
memblock tests: add top-down NUMA tests for memblock_alloc_try_nid*
memblock tests: add bottom-up NUMA tests for memblock_alloc_try_nid*
memblock tests: add generic NUMA tests for memblock_alloc_try_nid*
tools/testing/memblock/scripts/Makefile.include | 2 +-
tools/testing/memblock/tests/alloc_api.c | 223 ++-
tools/testing/memblock/tests/alloc_helpers_api.c | 52 +-
tools/testing/memblock/tests/alloc_nid_api.c | 1814 +++++++++++++++++++---
tools/testing/memblock/tests/alloc_nid_api.h | 16 +
tools/testing/memblock/tests/basic_api.c | 767 +++++++++
tools/testing/memblock/tests/common.c | 42 +-
tools/testing/memblock/tests/common.h | 86 +-
8 files changed, 2664 insertions(+), 338 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2022-10-11 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 10:37 Mike Rapoport [this message]
2022-10-12 2:37 ` [GIT PULL] memblock updates for v6.1 Linus Torvalds
2022-10-12 3:22 ` Mike Rapoport
2022-10-12 3:55 ` pr-tracker-bot
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=Y0VHfYkFUqYwVAru@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 \
--cc=rppt@linux.ibm.com \
--cc=shaoqin.huang@intel.com \
--cc=torvalds@linux-foundation.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 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.