From: Michael Schmitz <schmitzmic@googlemail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@googlemail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thorsten Glaser <tg@mirbsd.de>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards)
Date: Sun, 24 Apr 2011 14:19:28 +1200 [thread overview]
Message-ID: <4DB388B0.9030201@gmail.com> (raw)
In-Reply-To: <m2tydohp23.fsf@igel.home>
Andreas Schwab wrote:
> Michael Schmitz <schmitzmic@googlemail.com> writes:
>
>
>> Hi,
>>
>> node_present_pages(node) returns false:
>>
>> m68k_setup_node: node 0 addr 0 size 14680064
>> m68k_setup_node: node 0 not present!
>> m68k_setup_node: node 1 addr 16777216 size 268435456
>> m68k_setup_node: node 1 not present!
>>
>
> That's because paging_init calls m68k_setup_node before
> free_area_init_node, which is where node_present_pages is set.
>
>
Thanks - I had tried to move the code to just before the
free_area_init_node loop and given up there.
Much appreciated,
Michael
prev parent reply other threads:[~2011-04-24 2:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 8:19 Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Geert Uytterhoeven
2011-04-23 1:31 ` Michael Schmitz
2011-04-23 2:14 ` Michael Schmitz
2011-04-23 3:47 ` Michael Schmitz
2011-04-23 13:08 ` Geert Uytterhoeven
2011-04-23 15:39 ` Fix for SLUB? Thorsten Glaser
2011-04-23 18:57 ` Christian T. Steigies
2011-04-23 21:00 ` Debian/m68k kernel (preview) Thorsten Glaser
2011-04-24 4:00 ` Ben Hutchings
2011-04-24 11:18 ` Thorsten Glaser
2011-04-24 20:07 ` Thorsten Glaser
2011-04-25 3:08 ` Michael Schmitz
2011-04-24 2:06 ` Fix for SLUB? Michael Schmitz
2011-04-24 8:26 ` Geert Uytterhoeven
2011-04-23 17:09 ` Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Andreas Schwab
2011-04-24 2:19 ` Michael Schmitz [this message]
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=4DB388B0.9030201@gmail.com \
--to=schmitzmic@googlemail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
/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