From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: linux-mm@kvack.org, Yinghai Lu <yinghai@kernel.org>,
Stefan Hellermann <stefan@the2masters.de>,
akpm@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: flatmem broken for nommu? [Was: Re: does non-continuous RAM means I need to select the sparse memory model?]
Date: Thu, 1 Dec 2011 16:39:33 +0100 [thread overview]
Message-ID: <20111201153933.GL26618@pengutronix.de> (raw)
In-Reply-To: <20111201105718.GJ26618@pengutronix.de>
Hello,
On Thu, Dec 01, 2011 at 11:57:18AM +0100, Uwe Kleine-Konig wrote:
> On Tue, Nov 29, 2011 at 10:39:10PM -0200, Fabio Estevam wrote:
> > 2011/11/29 Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>:
> > > Hello,
> > >
> > > I'm currently working on a new arch port and my current machine has RAM
> > > at 0x10000000 and 0x80000000. So there is a big hole between the two
> > > banks. When selecting the sparse memory model it works, but when
> > > selecting flat the machine runs into a BUG in mark_bootmem() called by
> > > free_unused_memmap() to free the space between the two banks.
> >
> > My understanding is that you have to select ARCH_HAS_HOLES_MEMORYMODEL.
> I think that is not necessary.
>
> > > Is that expected (meaning I cannot use the flat model)? I currently
> > > don't have another machine handy that has >1 memory back to test that.
> >
> > In case you have access to a MX35PDK you can try on this board as it does have
> > the memory hole.
> No I havn't, but I just used a 128MB machine and changed that in the
> .fixup callback to 64MB + 32MB with a 32MB hole in between and it works
> fine without ARCH_HAS_HOLES_MEMORYMODEL.
>
> I debugged the problem a bit further and one symptom is that
>
> struct page *mem_map
>
> is NULL for me. That looks wrong. I guess this is just broken for nommu.
> I will dig into that later today.
The problem is that the memory for mem_map is allocated using:
map = alloc_bootmem_node_nopanic(pgdat, size);
without any error checking. The _nopanic was introduced by commit
8f389a99 (mm: use alloc_bootmem_node_nopanic() on really needed path)
I don't understand the commit's log and don't really see why it should
be allowed to not panic if the allocation failes here but use a NULL
pointer instead.
I put the people involved in 8f389a99 on Cc, maybe someone can comment?
Apart from that it seems I cannot use flatmem as is on my machine. It
has only 128kiB@0x10000000 + 1MiB@0x80000000 and needs 14MiB to hold the
table of "struct page"s. :-(
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-Konig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2011-12-01 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111129203010.GA26618@pengutronix.de>
[not found] ` <CAOMZO5DX_ZvCOu+pqZpJ7Ni2B=qmSFCZTHnuzKt==OsBsJZH=Q@mail.gmail.com>
[not found] ` <20111201105718.GJ26618@pengutronix.de>
2011-12-01 15:39 ` Uwe Kleine-König [this message]
2011-12-01 16:10 ` flatmem broken for nommu? [Was: Re: does non-continuous RAM means I need to select the sparse memory model?] Stefan Hellermann
2011-12-01 20:18 ` Uwe Kleine-König
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=20111201153933.GL26618@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=stefan@the2masters.de \
--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;
as well as URLs for NNTP newsgroup(s).