From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: linux-mm@kvack.org
Subject: Warning after "enforce overlap of memory.memblock and memory.reserved"
Date: Sat, 12 Dec 2020 20:37:49 +0100 [thread overview]
Message-ID: <de5c9f65-fe9c-f201-c9df-fa437d7d6d3e@gmail.com> (raw)
Since 950c37691925 ("mm: memblock: enforce overlap of memory.memblock
and memory.reserved") I get the following warning (on x86).
memblock: reserved range [0x0000000000000000-0x0000000000001000] is not in memory
memblock: reserved range [0x000000000009f000-0x0000000000100000] is not in memory
According to comment "Some architectures (e.g. x86) have reserved pages
outside of memblock.memory." it seems there's nothing wrong with it,
then why a warning? Wouldn't debug level be better suited?
next reply other threads:[~2020-12-12 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 19:37 Heiner Kallweit [this message]
2020-12-14 8:06 ` Mike Rapoport
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=de5c9f65-fe9c-f201-c9df-fa437d7d6d3e@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.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