From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix handling of memreserve if the range lands in highmem
Date: Wed, 09 Jan 2008 13:30:44 -0600 [thread overview]
Message-ID: <478520E4.1050204@freescale.com> (raw)
In-Reply-To: <3B831CF0-E978-42E7-BA26-7598BC27A5F6@kernel.crashing.org>
Kumar Gala wrote:
> On Jan 9, 2008, at 12:53 PM, Scott Wood wrote:
>> It looks like if the reserved area straddles the highmem boundary, it'll
>> only reserve the highmem portion.
>
> Yeah, I thought about that. I'm wondering if we should warn about
> this.. its seems like a bad thing to do.
How is the firmware supposed to know where Linux sets its lowmem limit?
I think this is something that needs to be handled.
-Scott
next prev parent reply other threads:[~2008-01-09 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 17:28 [PATCH] [POWERPC] Fix handling of memreserve if the range lands in highmem Kumar Gala
2008-01-09 18:53 ` Scott Wood
2008-01-09 19:27 ` Kumar Gala
2008-01-09 19:30 ` Scott Wood [this message]
2008-01-09 19:41 ` Kumar Gala
2008-01-09 19:52 ` Scott Wood
2008-01-10 6:02 ` Kumar Gala
2008-01-10 17:25 ` Scott Wood
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=478520E4.1050204@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).