WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] sparsemem/discontig?

Hi Jes,

I checked your old mail.
I might figure out your problem.

Xen/IPF assumes that the location of its kernel is starting at
physical address 0x4000000. And its virtual address must be
0xf000000004000000. Xen uses __pa() macro everywhere to get a physical
address of symbol which is declared inside kernel.

But it seems that your Altix box doesn't have such a lower addressed
physical memory.  I guess that your kernel is located from
0x3014000000 to 0x3018000000.  If so, __pa() macro doesn't work well
and `Unimplemented Data Address fault' would happen.

I'm not confident at all but please try modifying every value in
xen/arch/ia64/xen.lds.s as follows:
        0xf000000004000000 => 0xf000003014000000

Thanks,
Kouya

Jes Sorensen writes:
 > Right now I am getting this output from Xen on a small Altix (4 nodes,
 > 8 cpus, 6GB of RAM):
 > 
 > (XEN) Init boot pages: 0x3003000120 -> 0x3014000000.
 > (XEN) Init boot pages: 0x3018000000 -> 0x307bffc000.
 > (XEN) Init boot pages: 0xb003000000 -> 0xb07c000000.
 > (XEN) Init boot pages: 0x13003000000 -> 0x1303c000000.
 > (XEN) Init boot pages: 0x1b003000000 -> 0x1b038ec5000.
 > (XEN) Init boot pages: 0x1b039da8d20 -> 0x1b03a3a4010.
 > (XEN) Init boot pages: 0x1b03a3a4070 -> 0x1b03a3a7fcd.
 > (XEN) Init boot pages: 0x1b03a3a8010 -> 0x1b03a42c010.
 > (XEN) Init boot pages: 0x1b03a42cbe0 -> 0x1b03a7fc000.
 > (XEN) Init boot pages: 0x1b03b800000 -> 0x1b03bd64000.
 > (XEN) Init boot pages: 0x1b03bda0000 -> 0x1b03be10000.
 > (XEN) Init boot pages: 0x1b03be80000 -> 0x1b03bea0000.
 > 
 > I haven't checked yet whether the code receiving those tables does
 > anything with it to round up to granule alignment etc. otherwise it
 > could explain why the thing explodes for me.
 > 
 > But what it does is that it takes forever to get to the point where it
 > prints the total System RAM - in fact at first I thought the system
 > had crashed and only because I once left it for several minutes did I
 > end up seeing this output :(
 > 
 > Jes
 > 
 > _______________________________________________
 > Xen-ia64-devel mailing list
 > Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
 > http://lists.xensource.com/xen-ia64-devel


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