From: Geoff Levand <geoffrey.levand@am•sony.com>
To: Arnd Bergmann <arnd@arndb•de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
nhorman@redhat•com, David Woodhouse <dwmw2@infradead•org>,
cbe-oss-dev@ozlabs•org, Ben Collins <ben.collins@ubuntu•com>
Subject: Re: [Cbe-oss-dev] [PATCH] Ignore memory listed in PS3 device tree
Date: Tue, 03 Apr 2007 16:58:14 -0700 [thread overview]
Message-ID: <4612EA16.7070102@am.sony.com> (raw)
In-Reply-To: <200704040055.36173.arnd@arndb.de>
Arnd Bergmann wrote:
> On Wednesday 04 April 2007, Geoff Levand wrote:
>> So there are really two answers, one is that having the boot memory in=
the
>> DT hasn't changed, I just haven't finished that part yet. =EF=BF=BDThe=
other is that
>> we get the amount of memory at runtime because it is a dynamic resourc=
e, and
>> cannot be known at DT compile time.
>=20
> But the device tree can easily be modified before entering the new kern=
el,
> when the kboot kernel allocates all the memory it can get, it just need=
s
> to list it in the device tree in some preallocated device node.
Yes, but boot mem is not allocated by the guest, it is allocated by the p=
olicy
module. The guest can only query how much boot mem has been allocated fo=
r
it. This can be done by the bootloader, or the kernel itself, if done ea=
rly
enough. That info needs to be added to the DT before the kernel sets up =
its
boot mem structures. My current plan is to do it in the bootloader, sinc=
e
there is not a platform hook in the current powerpc arch code that is ear=
ly
enough.
But you seem to say we can do something in the first stage kernel and pas=
s
some info to the second stage kernel? The trouble with that is that when
the kernel is used as a first stage, where does the info come from? I wa=
nt
to have a single kernel that can be either programmed into flash or loade=
d
by kexec. For that to work the DT setup must be done in the wrapper, or
the kernel itself.
-Geoff
next prev parent reply other threads:[~2007-04-03 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 22:43 [PATCH] Ignore memory listed in PS3 device tree David Woodhouse
2007-03-29 23:23 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
2007-03-30 0:27 ` David Woodhouse
2007-03-30 13:25 ` Segher Boessenkool
2007-04-02 0:20 ` Michael Ellerman
2007-04-02 17:36 ` Segher Boessenkool
2007-04-03 2:42 ` Michael Ellerman
2007-04-03 3:16 ` David Woodhouse
2007-04-03 14:45 ` David Woodhouse
2007-04-03 21:18 ` Geoff Levand
2007-04-03 21:48 ` David Woodhouse
2007-04-03 22:45 ` Geoff Levand
2007-04-03 22:55 ` Arnd Bergmann
2007-04-03 23:58 ` Geoff Levand [this message]
2007-04-04 0:10 ` David Woodhouse
2007-04-04 11:43 ` Segher Boessenkool
2007-04-04 1:30 ` Benjamin Herrenschmidt
2007-04-04 1:28 ` Benjamin Herrenschmidt
2007-04-04 1:26 ` Benjamin Herrenschmidt
2007-03-30 17:41 ` Geoff Levand
2007-03-30 17:45 ` David Woodhouse
2007-03-30 18:11 ` Segher Boessenkool
2007-03-30 18:13 ` David Woodhouse
2007-03-31 15:27 ` Segher Boessenkool
2007-03-31 22:34 ` Benjamin Herrenschmidt
2007-03-31 22:42 ` David Woodhouse
2007-04-06 21:22 ` Geoff Levand
2007-04-06 22:34 ` Benjamin Herrenschmidt
2007-04-06 22:43 ` David Woodhouse
2007-04-06 23:15 ` Geoff Levand
2007-04-06 23:35 ` Benjamin Herrenschmidt
2007-04-06 23:44 ` David Woodhouse
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=4612EA16.7070102@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=arnd@arndb$(echo .)de \
--cc=ben.collins@ubuntu$(echo .)com \
--cc=cbe-oss-dev@ozlabs$(echo .)org \
--cc=dwmw2@infradead$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=nhorman@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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