All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Joshua Hahn <joshua.hahnjy@gmail.com>,
	Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: introduce check_pages boot parameter
Date: Sun, 7 Dec 2025 18:17:56 +0200	[thread overview]
Message-ID: <aTWotB5ev3q9VdXj@kernel.org> (raw)

Hi Linus,

The following changes since commit ac3fd01e4c1efce8f2c054cdeb2ddd2fc0fb150d:

  Linux 6.18-rc7 (2025-11-23 14:53:16 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-6.19-rc1

for you to fetch changes up to 83c8f7b5e194eaf3fb268c513e23e23e892de8ed:

  mm/mm_init: Introduce a boot parameter for check_pages (2025-12-04 19:40:25 +0200)

----------------------------------------------------------------
memblock: introduce check_pages boot parameter

... to decouple simple checks for page state on allocation and free from
CONFIG_DEBUG_VM.

check_pages parameter allows enabling page checking without building kernel
with CONFIG_DEBUG_VM or forcing init_on_{alloc, free} or other heavier
mechanisms.

----------------------------------------------------------------
Joshua Hahn (1):
      mm/mm_init: Introduce a boot parameter for check_pages

 Documentation/admin-guide/kernel-parameters.txt |  8 ++++++++
 mm/mm_init.c                                    | 10 +++++++++-
 2 files changed, 17 insertions(+), 1 deletion(-)

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2025-12-07 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07 16:17 Mike Rapoport [this message]
2025-12-07 16:57 ` [GIT PULL] memblock: introduce check_pages boot parameter 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=aTWotB5ev3q9VdXj@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=joshua.hahnjy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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.