From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
nhorman@redhat.com, David Woodhouse <dwmw2@infradead.org>,
cbe-oss-dev <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: Wed, 04 Apr 2007 11:30:45 +1000 [thread overview]
Message-ID: <1175650246.30879.41.camel@localhost.localdomain> (raw)
In-Reply-To: <4612D8FE.1070400@am.sony.com>
> There are several points here I feel need explanation. One is that memory
> is a dynamic resource allocated by the HV, so it needs to be managed as a
> dynamic resource by the guest OS.
That happens on pSeries too and we still keep the device-tree in check,
but that's related to the way all hotplug operations work on p... on
these, the HV provides us with device-tree updates.
I still think that the RMO is _not_ a dynamic resource, and as such
should be present in the memory node as this is expected of quite a few
things around including kexec tools.
> Another point is that the HV has two
> types of memory; boot memory, and virtual memory. Boot memory is what will
> be in is in the DT when I finish the zImage implementation. Virtual memory
> is what I currently have as hotplug memory.
>
> 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. The other is that
> we get the amount of memory at runtime because it is a dynamic resource, and
> cannot be known at DT compile time. It is just by some luck that the 2.6.16
> kernel continues to work correctly on the PS3, but it is not guaranteed to,
> and has a good chance of failing on non-ps3 systems that use the lv1 hypervisor.
Adding/removing memory outside of the RMO without updating the DT is
fine with me. The RMO itself should be in the DT though.
Ben.
next prev parent reply other threads:[~2007-04-04 1:30 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
2007-04-04 0:10 ` David Woodhouse
2007-04-04 11:43 ` Segher Boessenkool
2007-04-04 1:30 ` Benjamin Herrenschmidt [this message]
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=1175650246.30879.41.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ben.collins@ubuntu.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=geoffrey.levand@am.sony.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nhorman@redhat.com \
/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).