From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Benjamin Krill <ben@codiert.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: rtas instantiation when commandline contains mem
Date: Fri, 17 Jul 2009 16:48:49 +1000 [thread overview]
Message-ID: <1247813329.6101.7.camel@pasglop> (raw)
In-Reply-To: <20090717063620.GC22901@codiert.org>
On Fri, 2009-07-17 at 08:36 +0200, Benjamin Krill wrote:
> >> the rtas instantiation (prom_init.c) doesn't work correctly if the
> >> kernel parameter "mem=" is used. The current code doesn't evaluate
> >> the kernel parameter which causes the issue that alloc_down
> >> allocates somewhere in the "real" memory space. So it can
> >> happen that the allocation space is above "mem=".
> >>
> >> Commit 2babf5c2ec2f2d5de3e38d20f7df7fd815fd10c9 removes the
> >> evaluation of "mem=".
> >
> >Ah yes, we don't constraint prom_init.c to mem=, only the kernel
>
> Is that with intent? Or should I provide a patch to include it again?
Well I suppose it makes sense to include it again, not sure about that,
there's potentially a similar issue with TCE tables.
I understand what you are trying to do (though I told you I don't think
it's the right approach ;-) but heh... send a patch we'll see what it
looks like.
Cheers,
Ben.
next prev parent reply other threads:[~2009-07-17 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 13:12 rtas instantiation when commandline contains mem Benjamin Krill
2009-07-16 22:36 ` Benjamin Herrenschmidt
2009-07-17 6:36 ` Benjamin Krill
2009-07-17 6:48 ` Benjamin Herrenschmidt [this message]
2009-07-17 7:53 ` Michael Ellerman
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=1247813329.6101.7.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ben@codiert.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.