From: David Daney <ddaney@caviumnetworks.com>
To: Michael Sundius <msundius@cisco.com>
Cc: Kevin Cernekee <cernekee@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
David VomLehn <dvomlehn@cisco.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Andy Whitcroft <apw@shadowen.org>,
Jon Fraser <jfraser@broadcom.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2] MIPS: Kernel crashes on boot with SPARSEMEM + HIGHMEM enabled
Date: Fri, 01 Apr 2011 11:48:01 -0700 [thread overview]
Message-ID: <4D961DE1.50807@caviumnetworks.com> (raw)
In-Reply-To: <4D961C6A.9070808@cisco.com>
On 04/01/2011 11:41 AM, Michael Sundius wrote:
> David Daney wrote:
>>
>>
>> I think this may do the same thing as my patch:
>>
>> http://patchwork.linux-mips.org/patch/1988/
>>
>> Although my patch had different motivations, and changes some other
>> things around too.
>>
>> David Daney
>>
> I'm not really sure why your kernel or initrd would be in memory was not
> within
> the range that had been accounted for. are you saying its in high mem?
>
Well the memory initialization code has a bunch of weird rules built in
that prevent some memory from being used.
For example if the kernel resides in a different SPARSE page than the
rest of memory bad things happen because memory_present() was not called
on something that is later freed (when init memory is released).
If I try to put an initrd at a high physical address, the memory below
that is not usable.
My three patches try to make some sense out of the whole thing.
David Daney
prev parent reply other threads:[~2011-04-01 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 0:27 [PATCH v2] MIPS: Kernel crashes on boot with SPARSEMEM + HIGHMEM enabled Kevin Cernekee
2011-04-01 0:27 ` Kevin Cernekee
2011-04-01 16:56 ` David Daney
2011-04-01 17:31 ` Kevin Cernekee
2011-04-01 18:41 ` Michael Sundius
2011-04-01 18:48 ` David Daney [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=4D961DE1.50807@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=apw@shadowen.org \
--cc=cernekee@gmail.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dvomlehn@cisco.com \
--cc=jfraser@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=msundius@cisco.com \
--cc=ralf@linux-mips.org \
--cc=stable@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