From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com, mpe@ellerman.id.au
Subject: [PATCH] powerpc/mm: Fix mapped range information print during boot
Date: Fri, 28 Apr 2017 19:54:45 +0530 [thread overview]
Message-ID: <20170428142445.17615-1-khandual@linux.vnet.ibm.com> (raw)
This is a trivial fix patch regarding mapped ranges in radix MMU
environment during boot. No functional change.
Before the patch:
$dmesg | grep Mapped
[ 0.000000] Mapped range 0x0 - 0x2000000000 with 0x40000000
[ 0.000000] Mapped range 0x200000000000 - 0x202000000000 with 0x40000000
After the patch:
$dmesg | grep Mapped
[ 0.000000] Mapped range 0x0000000000000000 - 0x0000002000000000 with 1024 MB
[ 0.000000] Mapped range 0x0000200000000000 - 0x0000202000000000 with 1024 MB
Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
---
arch/powerpc/mm/pgtable-radix.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/pgtable-radix.c b/arch/powerpc/mm/pgtable-radix.c
index c28165d..802ead4 100644
--- a/arch/powerpc/mm/pgtable-radix.c
+++ b/arch/powerpc/mm/pgtable-radix.c
@@ -115,7 +115,8 @@ static inline void __meminit print_mapping(unsigned long start,
if (end <= start)
return;
- pr_info("Mapped range 0x%lx - 0x%lx with 0x%lx\n", start, end, size);
+ pr_info("Mapped range 0x%016lx - 0x%016lx with %lu MB\n",
+ start, end, (unsigned long) (size >> 20));
}
static int __meminit create_physical_mapping(unsigned long start,
--
2.9.3
next reply other threads:[~2017-04-28 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:24 Anshuman Khandual [this message]
2017-05-03 9:32 ` [PATCH] powerpc/mm: Fix mapped range information print during boot Michael Ellerman
2017-05-03 11:06 ` Anshuman Khandual
2017-08-31 11:35 ` Michael Ellerman
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=20170428142445.17615-1-khandual@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).