From: Yinghai Lu <yinghai@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: benh@kernel.crashing.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, torvalds@linux-foundation.org,
linux-arch@vger.kernel.org
Subject: Re: LMB bits
Date: Sat, 10 Jul 2010 13:53:55 -0700 [thread overview]
Message-ID: <4C38DDE3.9010303@kernel.org> (raw)
In-Reply-To: <20100710.131418.246532639.davem@davemloft.net>
On 07/10/2010 01:14 PM, David Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Sat, 10 Jul 2010 21:01:59 +1000
>
>> On Fri, 2010-07-09 at 20:55 -0700, David Miller wrote:
>>> A quick update, I'm still chipping away to find the culprit,
>>> I know so far that things are ok at least 14 patches into the
>>> series.
>>>
>>> I'll work more to try and track down the exact problem tomorrow.
>>
>> Thanks Dave !
>
> The first guilty commit seems to be:
>
> --------------------
>>From 869146ec57f449a5dd4bb5d939361841f4f7f3c6 Mon Sep 17 00:00:00 2001
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Tue, 6 Jul 2010 15:39:08 -0700
> Subject: [PATCH 01/12] memblock: Make memblock_find_region() out of memblock_alloc_region()
>
> This function will be used to locate a free area to put the new memblock
> arrays when attempting to resize them. memblock_alloc_region() is gone,
> the two callsites now call memblock_add_region().
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> --------------------
>
> I wonder if there is some subtle way you've changed behavior here?
> Previously if alloc block fails to do the add, it continues and
> keeps trying.
>
> Whereas now this add call happens a level higher and it's immediately
> signalled as a hard failure.
>
> Oh I see, your conversion of membase_alloc_nid_region() is buggy.
> Instead of passing in "ret" as the base address to memblock_add_region(),
> you're passing in the original value, "start".
>
> The other conversion was done correctly, which is why you didn't see
> this problem obviously :)
>
> I'll make this fix and see how much further I can get.
Ben/David,
can you fold in following patch in your patchset too?
also please use -v2 [PATCH] lmb: rename to memblock
that is removing one wrong change with microblaze dts
Thanks
Yinghai
Subject: [PATCH] memblock: memblock_find_base() should return MEMBLOCK_ERROR on failing path
all callees assume it return MEMBLOCK_ERROR when it fail to find a range
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/mm/memblock.c
===================================================================
--- linux-2.6.orig/mm/memblock.c
+++ linux-2.6/mm/memblock.c
@@ -154,7 +154,7 @@ static phys_addr_t __init memblock_find_
if (found != MEMBLOCK_ERROR)
return found;
}
- return 0;
+ return MEMBLOCK_ERROR;
}
static void memblock_remove_region(struct memblock_type *type, unsigned long r)
next prev parent reply other threads:[~2010-07-10 20:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278031351-23223-1-git-send-email-yinghai@kernel.org>
2010-07-09 7:11 ` LMB bits Benjamin Herrenschmidt
2010-07-09 7:24 ` Ingo Molnar
2010-07-09 7:28 ` David Miller
2010-07-09 7:33 ` Ingo Molnar
2010-07-09 8:24 ` Geert Uytterhoeven
2010-07-09 13:51 ` Ingo Molnar
2010-07-10 0:20 ` David Miller
2010-07-10 3:55 ` David Miller
2010-07-10 11:01 ` Benjamin Herrenschmidt
2010-07-10 20:14 ` David Miller
2010-07-10 20:53 ` Yinghai Lu [this message]
2010-07-12 3:24 ` Benjamin Herrenschmidt
2010-07-12 7:38 ` Benjamin Herrenschmidt
2010-07-12 22:34 ` David Miller
2010-07-13 7:12 ` Benjamin Herrenschmidt
2010-07-13 8:54 ` Ingo Molnar
2010-07-13 15:11 ` Linus Torvalds
2010-07-13 16:45 ` David Miller
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=4C38DDE3.9010303@kernel.org \
--to=yinghai@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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.