From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Konstantin Baydarov <kbaidarov@ru.mvista.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PowerPC] Support For Initrd Loaded Into Highmem
Date: Mon, 18 May 2009 07:56:17 +1000 [thread overview]
Message-ID: <1242597377.18075.1.camel@pasglop> (raw)
In-Reply-To: <20090517133417.9E0FC832E416@gemini.denx.de>
> > How Solved:
> > Code was added that checks if initrd is in the highmem and relocates initrd
> > into lowmem if required.
>
> I don't think this is needed. Just don't load the ramdisk to highmem
> in the first place.
Well, it does make some sense to avoid the kernel eating itself if
passed things out of lowmem in the reserve map, though Konstantin patch
doesn't fix that properly, I think it's still something to look into.
Cheers,
Ben.
next prev parent reply other threads:[~2009-05-17 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 16:44 [PATCH] [PowerPC] Support For Initrd Loaded Into Highmem Konstantin Baydarov
2009-05-17 13:34 ` Wolfgang Denk
2009-05-17 21:56 ` Benjamin Herrenschmidt [this message]
2009-05-17 21:55 ` Benjamin Herrenschmidt
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=1242597377.18075.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kbaidarov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.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