On Thu, 2007-01-04 at 14:15 -0700, Yoder Stuart-B08248 wrote: > I have turned on debug prints in arch/powerpc/boot_of.c. > One thing I'm puzzling over is why boot_of_alloc_init() > is marking overlapping regions of memory. Does that > make sense??
It doesn't exactly make sense, but in this case it's not a real problem... > [snip] > boot_of_alloc_init: marking 0x0 - 0x0^M > boot_of_alloc_init: marking 0x0 - 0x400^M These two come from your Open Firmware device tree. They don't make sense IMHO. systemsim may have a bug in its device tree. We could also have a bug in the way we parse the "available" property, but I believe our code has been tested on PowerMac and SLOF, and it looks correct to me. > boot_of_alloc_init: marking 0x400000 - 0x88b000^M This is our code reserving Xen's text, _start to _end. > boot_of_alloc_init: marking 0x0 - 0x3000^M This is our code reserving the exception handlers. -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
