[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [XenPPC] systemsim-gpul problems


  • To: "Hollis Blanchard" <hollisb@xxxxxxxxxx>
  • From: "Yoder Stuart-B08248" <stuart.yoder@xxxxxxxxxxxxx>
  • Date: Thu, 4 Jan 2007 14:15:23 -0700
  • Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 04 Jan 2007 13:15:09 -0800
  • List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
  • Thread-index: AccwPJta+v3Z4U/iSsSCWyLnx5SduwACFJ1Q
  • Thread-topic: [XenPPC] systemsim-gpul problems

> -----Original Message-----
> From: Hollis Blanchard [mailto:hollisb@xxxxxxxxxx] 
> Sent: Thursday, January 04, 2007 2:12 PM
> 
> Have you tried attaching GDB to systemsim to figure out 
> what's going on?
> 

I haven't used gdb w/ the simulator yet-- I need to 
figure out how to do that.

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??

    [snip]
    boot_of_alloc_init: marking 0x0 - 0x0^M
    boot_of_alloc_init: marking 0x0 - 0x400^M
    boot_of_alloc_init: marking 0x400000 - 0x88b000^M
    boot_of_alloc_init: marking 0x0 - 0x3000^M
    [snip]

Also, why is there a region w/ zero length?

Stuart

_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.