From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: tj@kernel.org, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: [PATCH 01/24] mm/memblock: debug: correct displaying of upper memory boundary
Date: Fri, 8 Nov 2013 18:41:37 -0500 [thread overview]
Message-ID: <1383954120-24368-2-git-send-email-santosh.shilimkar@ti.com> (raw)
In-Reply-To: <1383954120-24368-1-git-send-email-santosh.shilimkar@ti.com>
From: Grygorii Strashko <grygorii.strashko@ti.com>
When debugging is enabled (cmdline has "memblock=debug") the memblock
will display upper memory boundary per each allocated/freed memory range
wrongly. For example:
memblock_reserve: [0x0000009e7e8000-0x0000009e7ed000] _memblock_early_alloc_try_nid_nopanic+0xfc/0x12c
The 0x0000009e7ed000 is displayed instead of 0x0000009e7ecfff
Hence, correct this by changing formula used to calculate upper memory
boundary to (u64)base + size - 1 instead of (u64)base + size everywhere
in the debug messages.
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
mm/memblock.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 0ac412a..e03918e 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -545,7 +545,7 @@ int __init_memblock memblock_free(phys_addr_t base, phys_addr_t size)
{
memblock_dbg(" memblock_free: [%#016llx-%#016llx] %pF\n",
(unsigned long long)base,
- (unsigned long long)base + size,
+ (unsigned long long)base + size - 1,
(void *)_RET_IP_);
return __memblock_remove(&memblock.reserved, base, size);
@@ -557,7 +557,7 @@ int __init_memblock memblock_reserve(phys_addr_t base, phys_addr_t size)
memblock_dbg("memblock_reserve: [%#016llx-%#016llx] %pF\n",
(unsigned long long)base,
- (unsigned long long)base + size,
+ (unsigned long long)base + size - 1,
(void *)_RET_IP_);
return memblock_add_region(_rgn, base, size, MAX_NUMNODES);
--
1.7.9.5
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-08 23:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 23:41 [PATCH 00/24] mm: Use memblock interface instead of bootmem Santosh Shilimkar
2013-11-08 23:41 ` Santosh Shilimkar [this message]
2013-11-08 23:41 ` [PATCH 02/24] mm/memblock: debug: don't free reserved array if !ARCH_DISCARD_MEMBLOCK Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 03/24] mm/bootmem: remove duplicated declaration of __free_pages_bootmem() Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 04/24] mm/block: remove unnecessary inclusion of bootmem.h Santosh Shilimkar
2013-11-13 2:09 ` Jens Axboe
2013-11-13 23:10 ` Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 05/24] mm/memory_hotplug: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 06/24] mm/staging: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 07/24] mm/char: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 08/24] mm/memblock: drop WARN and use SMP_CACHE_BYTES as a default alignment Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 09/24] mm/memblock: Add memblock memory allocation apis Santosh Shilimkar
2013-12-03 0:31 ` Andrew Morton
2013-12-03 0:48 ` Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 10/24] mm/init: Use memblock apis for early memory allocations Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 11/24] mm/printk: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 12/24] mm/page_alloc: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 13/24] mm/power: " Santosh Shilimkar
2013-11-09 1:30 ` Rafael J. Wysocki
2013-11-09 19:08 ` Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 14/24] mm/lib/swiotlb: " Santosh Shilimkar
2013-11-09 16:55 ` Konrad Rzeszutek Wilk
2013-11-09 19:07 ` Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 15/24] mm/lib/cpumask: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 16/24] mm/sparse: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 17/24] mm/hugetlb: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 18/24] mm/page_cgroup: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 19/24] mm/percpu: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 20/24] mm/memory_hotplug: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 21/24] mm/firmware: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 22/24] mm/ARM: kernel: " Santosh Shilimkar
2013-11-08 23:41 ` [PATCH 23/24] mm/ARM: mm: " Santosh Shilimkar
2013-11-08 23:42 ` [PATCH 24/24] mm/ARM: OMAP: " Santosh Shilimkar
2013-11-29 16:50 ` [PATCH 00/24] mm: Use memblock interface instead of bootmem Santosh Shilimkar
2013-12-03 0:32 ` Andrew Morton
2013-12-03 0:40 ` Santosh Shilimkar
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=1383954120-24368-2-git-send-email-santosh.shilimkar@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=akpm@linux-foundation.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox