On Nov 21, 2006, at 5:41 PM, Amos Waterland wrote:
-(XEN) of_walk: /memory: phandle 0xf6
+(XEN) of_walk: /memory: phandle 0x129
(XEN) of_walk: /memory/available: 0x30
(XEN) of_walk: 0x00000000 0x00004000 0x00000000 0x00736000
(XEN) of_walk: 0x00000000 0x00772000 0x00000000 0x0088e000
Hi. I am getting a bad feeling about the above values.
Yeah, you should get a bad feeling about this.
This shows that SLOF is occupying:
0x73A000-0x772000
Xen/PPC is
linked at 0x00400000. Doesn't this mean that we could easily corrupt
our text if we believe these values, or if claim respects them?
Maybe I
am missing something ...
I believe that this range of memory is used _after_ we have been
"elf" loaded. It seems to move depending on how big Xen is.
However we do have an issue where SLOF memory claim method is bogus
and it seems that as we try to allocate memory we need to consult the
available property for space.
I never assumed that claim could give me memory but I assumed that it
would at least fail if the claim will step on something, I guess
we'll have to check that for ourselves for then we allocate space for
RTAS and the OFD.
-JX
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel
| 
Home