All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Faiyaz Mohammed <faiyazm@codeaurora.org>,
	vinmenon@codeaurora.org, Mike Rapoport <rppt@linux.ibm.com>,
	Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: debug enhancements
Date: Mon, 14 Dec 2020 15:17:31 +0200	[thread overview]
Message-ID: <20201214131731.GA247200@kernel.org> (raw)

Hi Linus,

The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:

  Linux 5.10-rc4 (2020-11-15 16:44:31 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 5bdba520c1b318578caffd325515b35d187f8a0e:

  mm: memblock: drop __init from memblock functions to make it inline (2020-11-17 17:38:25 +0200)

----------------------------------------------------------------
memblock: debug enhancements

Improve tracking of early memory allocations when memblock debug is
enabled:

* Add memblock_dbg() to memblock_phys_alloc_range() to get details about
  its usage
* Make memblock allocator wrappers actually inline to track their callers
  in memblock debug messages

----------------------------------------------------------------
Faiyaz Mohammed (2):
      mm: memblock: add more debug logs
      mm: memblock: drop __init from memblock functions to make it inline

 include/linux/memblock.h | 18 +++++++++---------
 mm/memblock.c            |  3 +++
 2 files changed, 12 insertions(+), 9 deletions(-)

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2020-12-14 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 13:17 Mike Rapoport [this message]
2020-12-16 23:10 ` [GIT PULL] memblock: debug enhancements 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=20201214131731.GA247200@kernel.org \
    --to=rppt@kernel.org \
    --cc=faiyazm@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vinmenon@codeaurora.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.