date:20070122

Re: [XenPPC] Introducing BSC

2007-01-22 Thread Hollis Blanchard

What exact model do you have: 8842-21X, 8842-41X, or 8842-42X? I assume
you have a lot of them?

-- 
Hollis Blanchard
IBM Linux Technology Center

On Mon, 2007-01-22 at 22:31 +0100, Mario Macías wrote:
> Hi Hollis,
> We are using  JS20 machines.
> Regards
> 
> En/na Hollis Blanchard ha escrit:
> > On Mon, 2007-01-22 at 11:03 +0100, Mario Macías wrote:
> >
> >> Dear Xen-PPC team,
> >>
> >>  first of all I want to congratulate you for the great work you are
> >> doing with the Xen Power PC porting.
> >>
> >>   Let me introduce myself: my name is Mario Macías, from Barcelona
> >> Supercomputing Center ( http://www.bsc.es ). We are absolutely
> >> interested in the usage of Xen for our research systems and, in the
> >> future, for production environment.
> >>
> >>  Unfortunately, for the moment we cannot contribute with coding, but
> >> we expect to contribute to the improvement of Xen with our testing
> >> into research applications.
> >>
> >
> > Hi Mario, nice to meet you. :) What sort of PowerPC systems do you plan
> > to use Xen on?
> >
> >



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

[XenPPC] [xenppc-unstable] [XEN][POWERPC] Linker script simplification broke optimized builds.

2007-01-22 Thread Xen patchbot-xenppc-unstable

# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 8b7a8c2e0178f326cfef9fa01a5042a52503dacc
# Parent  d301edbf6ecec86d24573e4be3399fbf3a4bd463
[XEN][POWERPC] Linker script simplification broke optimized builds.

offending changeset was: changeset:   14126:c759c733f77d
So put it back and just update the symbols like a good little boy.

Signed-off-by: Jimi Xenidis <[EMAIL PROTECTED]>
---
 xen/arch/powerpc/xen.lds.S |  182 ++---
 1 files changed, 141 insertions(+), 41 deletions(-)

diff -r d301edbf6ece -r 8b7a8c2e0178 xen/arch/powerpc/xen.lds.S
--- a/xen/arch/powerpc/xen.lds.SMon Jan 22 13:01:31 2007 -0500
+++ b/xen/arch/powerpc/xen.lds.SMon Jan 22 15:52:46 2007 -0500
@@ -7,62 +7,113 @@ OUTPUT_FORMAT("elf64-powerpc", "elf64-po
  "elf64-powerpc")
 OUTPUT_ARCH(powerpc:common64)
 ENTRY(_start)
+SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64"); 
SEARCH_DIR("=/usr/lib64"); SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib"); 
SEARCH_DIR("=/usr/lib");
+/* Do we need any of these for elf?
+   __DYNAMIC = 0;*/
 PHDRS
 {
   text PT_LOAD;
 }   
 SECTIONS
 {
-  /* This is the address that we are linking at */ 
   . = 0x0040;
   PROVIDE(_text = .);
   PROVIDE(_stext = .);
   /* Read-only sections, merged into text segment: */
+  .interp : { *(.interp) } :text
+  .hash   : { *(.hash) }
+  .dynsym : { *(.dynsym) }
+  .dynstr : { *(.dynstr) }
+  .gnu.version: { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rel.dyn:
+{
+  *(.rel.init)
+  *(.rel.text .rel.text.* .rel.gnu.linkonce.t.*)
+  *(.rel.fini)
+  *(.rel.rodata .rel.rodata.* .rel.gnu.linkonce.r.*)
+  *(.rel.data .rel.data.* .rel.gnu.linkonce.d.*)
+  *(.rel.tdata .rel.tdata.* .rel.gnu.linkonce.td.*)
+  *(.rel.tbss .rel.tbss.* .rel.gnu.linkonce.tb.*)
+  *(.rel.ctors)
+  *(.rel.dtors)
+  *(.rel.got)
+  *(.rel.sdata .rel.sdata.* .rel.gnu.linkonce.s.*)
+  *(.rel.sbss .rel.sbss.* .rel.gnu.linkonce.sb.*)
+  *(.rel.sdata2 .rel.sdata2.* .rel.gnu.linkonce.s2.*)
+  *(.rel.sbss2 .rel.sbss2.* .rel.gnu.linkonce.sb2.*)
+  *(.rel.bss .rel.bss.* .rel.gnu.linkonce.b.*)
+}
+  .rela.dyn   :
+{
+  *(.rela.init)
+  *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+  *(.rela.fini)
+  *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+  *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+  *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+  *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+  *(.rela.ctors)
+  *(.rela.dtors)
+  *(.rela.got)
+  *(.rela.toc)
+  *(.rela.sdata .rela.sdata.* .rela.gnu.linkonce.s.*)
+  *(.rela.sbss .rela.sbss.* .rela.gnu.linkonce.sb.*)
+  *(.rela.sdata2 .rela.sdata2.* .rela.gnu.linkonce.s2.*)
+  *(.rela.sbss2 .rela.sbss2.* .rela.gnu.linkonce.sb2.*)
+  *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+}
+  .rel.plt: { *(.rel.plt) }
+  .rela.plt   : { *(.rela.plt) }
+  .rela.tocbss   : { *(.rela.tocbss) }
+  .init   :
+  {
+KEEP (*(.init))
+  } =0x6000
   .text   :
   {
-*(.text)
+*(.text .stub .text.* .gnu.linkonce.t.*)
 /* .gnu.warning sections are handled specially by elf32.em.  */
 *(.gnu.warning)
-  } : text
-  /* end of text */
+*(.sfpr .glink)
+  } =0x6000
+  .fini   :
+  {
+KEEP (*(.fini))
+  } =0x6000
   PROVIDE (__etext = .);
   PROVIDE (_etext = .);
   PROVIDE (etext = .);
-
-  /* read only data */
-  .rodata : { *(.rodata .rodata.*) } : text
-  .rodata1: { *(.rodata1) } : text
-  .sdata2 : { *(.sdata2 .sdata2.*) } : text
-  .sbss2  : { *(.sbss2 .sbss2.*) } : text
-
-  . = ALIGN(64);
-  __start___ex_table = .;
-  __ex_table : { *(__ex_table) } : text
-  __stop___ex_table = .;
-  . = ALIGN(64);
-
+  .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1: { *(.rodata1) }
+  .sdata2 : { *(.sdata2 .sdata2.* .gnu.linkonce.s2.*) }
+  .sbss2  : { *(.sbss2 .sbss2.* .gnu.linkonce.sb2.*) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+ the same address within the page on the next page up.  */
+  . = ALIGN (0x1) - ((0x1 - .) & (0x1 - 1)); . = 
DATA_SEGMENT_ALIGN (0x1, 0x1000);
+  /* Ensure the __preinit_array_start label is properly aligned.  We
+ could instead move the label definition inside the section, but
+ the linker would then create the section even if it turns out to
+ be empty, which isn't pretty.  */
+  . = ALIGN(64 / 8);
+  PROVIDE (__preinit_array_start = .);
+  .preinit_array : { *(.preinit_array) }
+  PROVIDE (__preinit_array_end = .);
+  PROVIDE (__init_array_start = .);
+  .init_array : { *(.init_array) }
+  PROVIDE (__init_array_end = .);
+

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

2007-01-22 Thread Hollis Blanchard

Hi Mark, you didn't mention this but I understand you are loading your
dom0 in an unusual way. Does this patch solve your problem?

diff -r ed5ee9dde0bd xen/arch/powerpc/boot_of.c
--- a/xen/arch/powerpc/boot_of.cSun Jan 21 08:17:46 2007 -0500
+++ b/xen/arch/powerpc/boot_of.cMon Jan 22 16:14:28 2007 -0600
@@ -488,6 +488,23 @@ static void boot_of_free(ulong addr, ulo
 }
 #endif
 
+static void boot_of_reserve(ulong addr, ulong size)
+{
+ulong bits;
+ulong pos;
+ulong i;
+
+size = ALIGN_UP(size, PAGE_SIZE);
+bits = size >> PAGE_SHIFT;
+pos = addr >> PAGE_SHIFT;
+
+for (i = 0; i < bits; i++) {
+if (test_bit(pos + i, mem_available_pages))
+of_panic("%s: pg :0x%lx already reserved.\n", __func__, pos + i);
+set_bit(pos + i, mem_available_pages);
+}
+}
+
 static ulong boot_of_alloc(ulong size)
 {
 ulong bits;
@@ -1121,6 +1138,7 @@ static void * __init boot_of_module(ulon
 /* was it handed to us in registers ? */
 mod0_start = r3;
 mod0_size = r4;
+boot_of_reserve(r3, r4);
 of_printf("%s: Dom0 was loaded and found using r3/r4:"
   "0x%lx[size 0x%lx]\n",
   __func__, mod0_start, mod0_size);


-- 
Hollis Blanchard
IBM Linux Technology Center

On Mon, 2007-01-22 at 15:31 -0500, Mark F Mergen wrote:
> 
> I cannot replicate Stuart's successful report.  I'm sure my simulator
> is a much older build than his and Hollis' guess about device trees is
> another reason I should bring my simulator up to date.  I apologize
> for raising a problem without doing that first.  I might not get to it
> right away, but I will do it.  Hollis, why don't you not waste your
> time with simulator until I test with a current one. 
> 
> Mark 
> 



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

Re: [XenPPC] Introducing BSC

2007-01-22 Thread Mario Macías


Hi Hollis,
We are using  JS20 machines.
Regards

En/na Hollis Blanchard ha escrit:

On Mon, 2007-01-22 at 11:03 +0100, Mario Macías wrote:
  

Dear Xen-PPC team,

 first of all I want to congratulate you for the great work you are
doing with the Xen Power PC porting.

  Let me introduce myself: my name is Mario Macías, from Barcelona
Supercomputing Center ( http://www.bsc.es ). We are absolutely
interested in the usage of Xen for our research systems and, in the
future, for production environment.

 Unfortunately, for the moment we cannot contribute with coding, but
we expect to contribute to the improvement of Xen with our testing
into research applications.



Hi Mario, nice to meet you. :) What sort of PowerPC systems do you plan
to use Xen on?

  



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

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

2007-01-22 Thread Mark F Mergen

I cannot replicate Stuart's successful report.  I'm sure my simulator is a 
much older build than his and Hollis' guess about device trees is another 
reason I should bring my simulator up to date.  I apologize for raising a 
problem without doing that first.  I might not get to it right away, but I 
will do it.  Hollis, why don't you not waste your time with simulator 
until I test with a current one.

Mark




"Yoder Stuart-B08248" <[EMAIL PROTECTED]> 
01/22/2007 01:58 PM

To
[EMAIL PROTECTED], Mark F Mergen/Watson/[EMAIL PROTECTED]
cc

Subject
RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on 
Mambo







I just did a clean build of top of tree Xen and Linux and
am able to boot my dom0 kernel on Xen with the simulator.
So I'm not seeing the same issue Mark had.

Mark-- I would try the very latest just to make sure.  I
built with linux changeset ab3b5849331d and Xen changeset
ed5ee9dde0bd.

It is taking a heck of a long time though.  The simulator
cycle count appears to have about doubled.

Stuart 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Hollis Blanchard
> Sent: Monday, January 22, 2007 12:02 PM
> To: Mark F Mergen
> Cc: xen-ppc-devel@lists.xensource.com
> Subject: Re: [XenPPC] Changeset with 3 files on Friday (I 
> think) has brokenXen on Mambo
> 
> Hi Mark, it was probably changeset 5bcb155e5de5 that caused 
> this. Could
> you open a bug (http://bugzilla.xensource.com/), assign it to me, and
> attach the full boot log? (It looks like you trimmed some of the early
> messages below.)
> 
> In the meantime I'll try to install systemsim locally, but it 
> looks like
> it doesn't play nicely with current distributions. My first guess is
> that systemsim's device tree memory nodes are wrong somehow.
> 
> It looks like you could simply revert the changeset in 
> question, but to
> avoid merge problems in the future, it would be better to fall back to
> the tree before that changeset went in (hg update -C $(hg parents -qr
> 5bcb155e5de5)).
> 
> Thanks!
> 
> -- 
> Hollis Blanchard
> IBM Linux Technology Center
> 
> 
> On Sun, 2007-01-21 at 19:24 -0500, Mark F Mergen wrote:
> > 
> > From the standpoint of us Lone Rangers using Mambo (Stuart and me),
> > things are broken again.  Below is the result of trying to 
> boot (this
> > is an unpatched system, doesn't contain any of my mods) 
> after applying
> > a single changeset with 3 files that I think was pushed on 
> Friday.  I
> > pulled it, it built OK, I ran out of time to test then, and I
> > discarded the email that described the changeset.  I'm 
> guessing, but I
> > think it may have been the same changeset that was sent 
> again Saturday
> > with the subject line "[XenPPC] [xenppc-unstable] [XEN][POWERPC]
> > merge" and affected these files: 
> >  xen/arch/powerpc/boot_of.c   |   39 +++
> > xen/arch/powerpc/memory.c|  150
> > ---
> > xen/include/asm-powerpc/mm.h |3 
> > 3 files changed, 98 insertions(+), 94 deletions(-) 
> > 
> > The problem appears to be at the lines highlighted in red 
> below.  Any
> > help or ideas in fixing this will be much appreciated. 
> > 
> > 211611123: (211859452): (XEN) Trying Dom0 as 64bit ELF 
> > 211648608: (211896989): (XEN) *** LOADING DOMAIN 0 *** 
> > 22000: [0]: (PC:0x0041B654) :   2224.2 Kilo-Inst/Sec :
> > .2 Kilo-Cycles/Sec 
> > 227352925: (227633054): (XEN) xen_start_info: 07ffe000 
> > 227371602: (227651740): (XEN) shared_info: 
> 0x3fff000,07fff000 
> > 227390712: (227670857): (XEN) loading OFH: 0x600, RMA: 
> 0x200 
> > 227506947: (227787248): (XEN) loading OFD: 0x6024000 RMA: 0x2024000,
> > 0x3 
> > 227590077: (227870488): (XEN) loading 64-bit Dom0: 0x6054000, in
> > RMA:0x2054000 
> > 230086980: (230371430): (XEN) no initrd 
> > 230096126: (230380580): (XEN) DOM: pc = 0x2054000, r2 = 0x0 
> > 230110154: (230394612): (XEN) Add /openprom props 
> > 230127650: (230412122): (XEN) Add /options props 
> > 230141413: (230425891): (XEN) Add /cpus props 
> > 230171687: (230456207): (XEN) Add /chosen props 
> > 230185151: (230469678): (XEN) DOM0 bootargs: init=/bin/bash 
> iommu=off
> > lpj=0x26 
> > 230211575: (230496117): (XEN) Remove /chosen/mmu, stub will replace 
> > 230229344: (230513891): (XEN) fix /memory props 
> > 230275249: (230559867): (XEN) Dom0: /[EMAIL PROTECTED]: ,
> > 0400 
> > 230304736: (230589372): (XEN) Dom0: /[EMAIL PROTECTED]: 
> 0400,
> > 0800 
> > 230327662: (230612304): (XEN) fix /xen props 
> > 230345978: (230630636): (XEN) Remove original /dart 
> > 230365995: (230650671): (XEN) Remove original /rtas 
> > 230413320: (230698061): (XEN) Assertion 
> 'allocated_in_map(first_page +
> > i)' failed, line 147, file page_alloc.c 
> > 230445056: (230729810): (XEN) BUG at page_alloc.c:147 
> > 230458933: (230743693): (XEN) [ Xen-3.0-unstable ] 
> > 23047

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

2007-01-22 Thread Yoder Stuart-B08248


I just did a clean build of top of tree Xen and Linux and
am able to boot my dom0 kernel on Xen with the simulator.
So I'm not seeing the same issue Mark had.

Mark-- I would try the very latest just to make sure.  I
built with linux changeset ab3b5849331d and Xen changeset
ed5ee9dde0bd.

It is taking a heck of a long time though.  The simulator
cycle count appears to have about doubled.

Stuart 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Hollis Blanchard
> Sent: Monday, January 22, 2007 12:02 PM
> To: Mark F Mergen
> Cc: xen-ppc-devel@lists.xensource.com
> Subject: Re: [XenPPC] Changeset with 3 files on Friday (I 
> think) has brokenXen on Mambo
> 
> Hi Mark, it was probably changeset 5bcb155e5de5 that caused 
> this. Could
> you open a bug (http://bugzilla.xensource.com/), assign it to me, and
> attach the full boot log? (It looks like you trimmed some of the early
> messages below.)
> 
> In the meantime I'll try to install systemsim locally, but it 
> looks like
> it doesn't play nicely with current distributions. My first guess is
> that systemsim's device tree memory nodes are wrong somehow.
> 
> It looks like you could simply revert the changeset in 
> question, but to
> avoid merge problems in the future, it would be better to fall back to
> the tree before that changeset went in (hg update -C $(hg parents -qr
> 5bcb155e5de5)).
> 
> Thanks!
> 
> -- 
> Hollis Blanchard
> IBM Linux Technology Center
> 
> 
> On Sun, 2007-01-21 at 19:24 -0500, Mark F Mergen wrote:
> > 
> > From the standpoint of us Lone Rangers using Mambo (Stuart and me),
> > things are broken again.  Below is the result of trying to 
> boot (this
> > is an unpatched system, doesn't contain any of my mods) 
> after applying
> > a single changeset with 3 files that I think was pushed on 
> Friday.  I
> > pulled it, it built OK, I ran out of time to test then, and I
> > discarded the email that described the changeset.  I'm 
> guessing, but I
> > think it may have been the same changeset that was sent 
> again Saturday
> > with the subject line "[XenPPC] [xenppc-unstable] [XEN][POWERPC]
> > merge" and affected these files: 
> >  xen/arch/powerpc/boot_of.c   |   39 +++
> > xen/arch/powerpc/memory.c|  150
> > ---
> > xen/include/asm-powerpc/mm.h |3 
> > 3 files changed, 98 insertions(+), 94 deletions(-) 
> > 
> > The problem appears to be at the lines highlighted in red 
> below.  Any
> > help or ideas in fixing this will be much appreciated. 
> > 
> > 211611123: (211859452): (XEN) Trying Dom0 as 64bit ELF 
> > 211648608: (211896989): (XEN) *** LOADING DOMAIN 0 *** 
> > 22000: [0]: (PC:0x0041B654) :   2224.2 Kilo-Inst/Sec :
> > .2 Kilo-Cycles/Sec 
> > 227352925: (227633054): (XEN) xen_start_info: 07ffe000 
> > 227371602: (227651740): (XEN) shared_info: 
> 0x3fff000,07fff000 
> > 227390712: (227670857): (XEN) loading OFH: 0x600, RMA: 
> 0x200 
> > 227506947: (227787248): (XEN) loading OFD: 0x6024000 RMA: 0x2024000,
> > 0x3 
> > 227590077: (227870488): (XEN) loading 64-bit Dom0: 0x6054000, in
> > RMA:0x2054000 
> > 230086980: (230371430): (XEN) no initrd 
> > 230096126: (230380580): (XEN) DOM: pc = 0x2054000, r2 = 0x0 
> > 230110154: (230394612): (XEN) Add /openprom props 
> > 230127650: (230412122): (XEN) Add /options props 
> > 230141413: (230425891): (XEN) Add /cpus props 
> > 230171687: (230456207): (XEN) Add /chosen props 
> > 230185151: (230469678): (XEN) DOM0 bootargs: init=/bin/bash 
> iommu=off
> > lpj=0x26 
> > 230211575: (230496117): (XEN) Remove /chosen/mmu, stub will replace 
> > 230229344: (230513891): (XEN) fix /memory props 
> > 230275249: (230559867): (XEN) Dom0: /[EMAIL PROTECTED]: ,
> > 0400 
> > 230304736: (230589372): (XEN) Dom0: /[EMAIL PROTECTED]: 
> 0400,
> > 0800 
> > 230327662: (230612304): (XEN) fix /xen props 
> > 230345978: (230630636): (XEN) Remove original /dart 
> > 230365995: (230650671): (XEN) Remove original /rtas 
> > 230413320: (230698061): (XEN) Assertion 
> 'allocated_in_map(first_page +
> > i)' failed, line 147, file page_alloc.c 
> > 230445056: (230729810): (XEN) BUG at page_alloc.c:147 
> > 230458933: (230743693): (XEN) [ Xen-3.0-unstable ] 
> > 230475250: (230760017): (XEN) CPU:    DOMID: 7fff 
> > 230494869: (230779651): (XEN) pc  msr
> >  
> > 230511907: (230796695): (XEN) lr  ctr
> >  
> > 230528990: (230813784): (XEN) srr0  srr1
> >  
> > 230551178: (230835986): (XEN) dar  dsisr 
>  ***
> > saved 
> > 230569931: (230854745): (XEN) dar  dsisr 
>  ***
> > actual 
> > 230593314: (230878143): (XEN) r00:  
> >   
> > 230625169: (230910016): (XEN) r04: 00

[XenPPC] [xenppc-unstable] [XEN][POWERPC] fill in arch_vcpu_reset()

2007-01-22 Thread Xen patchbot-xenppc-unstable

# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID bd937e22541db922863c93ea4062002def26a452
# Parent  bbd2af302fea7fdd704079779753afa74523945d
[XEN][POWERPC] fill in arch_vcpu_reset()
it panics now

Signed-off-by: Jimi Xenidis <[EMAIL PROTECTED]>
---
 xen/arch/powerpc/domain.c |7 +++
 1 files changed, 7 insertions(+)

diff -r bbd2af302fea -r bd937e22541d xen/arch/powerpc/domain.c
--- a/xen/arch/powerpc/domain.c Sun Jan 21 08:58:11 2007 -0500
+++ b/xen/arch/powerpc/domain.c Sun Jan 21 09:12:57 2007 -0500
@@ -173,6 +173,13 @@ int arch_set_info_guest(struct vcpu *v, 
 return 0;
 }
 
+int arch_vcpu_reset(struct vcpu *v)
+{
+panic("%s: called for Dom%d[%d]\n",
+  __func__, v->domain->domain_id, v->vcpu_id);
+return 0;
+}
+
 void dump_pageframe_info(struct domain *d)
 {
 struct page_info *page;

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

RE: [XenPPC] Build/config the world!

2007-01-22 Thread Yoder Stuart-B08248


I've build and built everything and ran into 1 warning that caused my
Xen build to break:

diff -r ed5ee9dde0bd xen/arch/powerpc/memory.c
--- a/xen/arch/powerpc/memory.c Sun Jan 21 08:17:46 2007 -0500
+++ b/xen/arch/powerpc/memory.c Mon Jan 22 11:55:06 2007 -0600
@@ -120,7 +120,7 @@ void memory_init(module_t *mod, int mcou
 {
 ulong eomem;
 ulong bitmap_start = ~0UL;
-ulong bitmap_end;
+ulong bitmap_end = ~0UL;
 ulong bitmap_size;
 ulong xh_pages;
 ulong start;
 
Not sure what the correct init value is, but gcc is complaining that
bitmap_end may be used uninitialized.

Stuart

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Jimi Xenidis
> Sent: Monday, January 22, 2007 6:49 AM
> To: xen-ppc-devel
> Subject: [XenPPC] Build/config the world!
> 
> In case you missed it, a lot has been going on so please:
>   1. reconfigure and build your linux
>   2. rebuild your Xen management tools (make install-tools)
>   3. and don't forget to rebuild xen :)
> 
> -JX
> 
> 
> ___
> Xen-ppc-devel mailing list
> Xen-ppc-devel@lists.xensource.com
> http://lists.xensource.com/xen-ppc-devel
> 

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

Re: [XenPPC] Changeset with 3 files on Friday (I think) has broken Xen on Mambo

2007-01-22 Thread Hollis Blanchard

Hi Mark, it was probably changeset 5bcb155e5de5 that caused this. Could
you open a bug (http://bugzilla.xensource.com/), assign it to me, and
attach the full boot log? (It looks like you trimmed some of the early
messages below.)

In the meantime I'll try to install systemsim locally, but it looks like
it doesn't play nicely with current distributions. My first guess is
that systemsim's device tree memory nodes are wrong somehow.

It looks like you could simply revert the changeset in question, but to
avoid merge problems in the future, it would be better to fall back to
the tree before that changeset went in (hg update -C $(hg parents -qr
5bcb155e5de5)).

Thanks!

-- 
Hollis Blanchard
IBM Linux Technology Center


On Sun, 2007-01-21 at 19:24 -0500, Mark F Mergen wrote:
> 
> From the standpoint of us Lone Rangers using Mambo (Stuart and me),
> things are broken again.  Below is the result of trying to boot (this
> is an unpatched system, doesn't contain any of my mods) after applying
> a single changeset with 3 files that I think was pushed on Friday.  I
> pulled it, it built OK, I ran out of time to test then, and I
> discarded the email that described the changeset.  I'm guessing, but I
> think it may have been the same changeset that was sent again Saturday
> with the subject line "[XenPPC] [xenppc-unstable] [XEN][POWERPC]
> merge" and affected these files: 
>  xen/arch/powerpc/boot_of.c   |   39 +++
> xen/arch/powerpc/memory.c|  150
> ---
> xen/include/asm-powerpc/mm.h |3 
> 3 files changed, 98 insertions(+), 94 deletions(-) 
> 
> The problem appears to be at the lines highlighted in red below.  Any
> help or ideas in fixing this will be much appreciated. 
> 
> 211611123: (211859452): (XEN) Trying Dom0 as 64bit ELF 
> 211648608: (211896989): (XEN) *** LOADING DOMAIN 0 *** 
> 22000: [0]: (PC:0x0041B654) :   2224.2 Kilo-Inst/Sec :
> .2 Kilo-Cycles/Sec 
> 227352925: (227633054): (XEN) xen_start_info: 07ffe000 
> 227371602: (227651740): (XEN) shared_info: 0x3fff000,07fff000 
> 227390712: (227670857): (XEN) loading OFH: 0x600, RMA: 0x200 
> 227506947: (227787248): (XEN) loading OFD: 0x6024000 RMA: 0x2024000,
> 0x3 
> 227590077: (227870488): (XEN) loading 64-bit Dom0: 0x6054000, in
> RMA:0x2054000 
> 230086980: (230371430): (XEN) no initrd 
> 230096126: (230380580): (XEN) DOM: pc = 0x2054000, r2 = 0x0 
> 230110154: (230394612): (XEN) Add /openprom props 
> 230127650: (230412122): (XEN) Add /options props 
> 230141413: (230425891): (XEN) Add /cpus props 
> 230171687: (230456207): (XEN) Add /chosen props 
> 230185151: (230469678): (XEN) DOM0 bootargs: init=/bin/bash iommu=off
> lpj=0x26 
> 230211575: (230496117): (XEN) Remove /chosen/mmu, stub will replace 
> 230229344: (230513891): (XEN) fix /memory props 
> 230275249: (230559867): (XEN) Dom0: /[EMAIL PROTECTED]: ,
> 0400 
> 230304736: (230589372): (XEN) Dom0: /[EMAIL PROTECTED]: 0400,
> 0800 
> 230327662: (230612304): (XEN) fix /xen props 
> 230345978: (230630636): (XEN) Remove original /dart 
> 230365995: (230650671): (XEN) Remove original /rtas 
> 230413320: (230698061): (XEN) Assertion 'allocated_in_map(first_page +
> i)' failed, line 147, file page_alloc.c 
> 230445056: (230729810): (XEN) BUG at page_alloc.c:147 
> 230458933: (230743693): (XEN) [ Xen-3.0-unstable ] 
> 230475250: (230760017): (XEN) CPU:    DOMID: 7fff 
> 230494869: (230779651): (XEN) pc  msr
>  
> 230511907: (230796695): (XEN) lr  ctr
>  
> 230528990: (230813784): (XEN) srr0  srr1
>  
> 230551178: (230835986): (XEN) dar  dsisr  ***
> saved 
> 230569931: (230854745): (XEN) dar  dsisr  ***
> actual 
> 230593314: (230878143): (XEN) r00:  
>   
> 230625169: (230910016): (XEN) r04:  
>   
> 230657026: (230941889): (XEN) r08:  
>   
> 230688919: (230973799): (XEN) r12:  
>   
> 230720813: (231005709): (XEN) r16:  
>   
> 230752705: (231037619): (XEN) r20:  
>   
> 230784598: (231069529): (XEN) r24:  
>   
> 230816491: (231101439): (XEN) r28:  
>   
> 230846833: (231131795): (XEN)  
> 230850876: (231135839): (XEN)
>  
> 230868629: (231153597): (XEN) Panic on CPU 0: 
> 230878253: (231163223): (XEN) BUG at page_alloc.c:147 
> 230891194: (

Re: [XenPPC] Introducing BSC

2007-01-22 Thread Hollis Blanchard

On Mon, 2007-01-22 at 11:03 +0100, Mario Macías wrote:
> Dear Xen-PPC team,
> 
>  first of all I want to congratulate you for the great work you are
> doing with the Xen Power PC porting.
> 
>   Let me introduce myself: my name is Mario Macías, from Barcelona
> Supercomputing Center ( http://www.bsc.es ). We are absolutely
> interested in the usage of Xen for our research systems and, in the
> future, for production environment.
> 
>  Unfortunately, for the moment we cannot contribute with coding, but
> we expect to contribute to the improvement of Xen with our testing
> into research applications.

Hi Mario, nice to meet you. :) What sort of PowerPC systems do you plan
to use Xen on?

-- 
Hollis Blanchard
IBM Linux Technology Center


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

[XenPPC] Build/config the world!

2007-01-22 Thread Jimi Xenidis


In case you missed it, a lot has been going on so please:
 1. reconfigure and build your linux
 2. rebuild your Xen management tools (make install-tools)
 3. and don't forget to rebuild xen :)

-JX


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

[XenPPC] Introducing BSC

2007-01-22 Thread Mario Macías


Dear Xen-PPC team,

first of all I want to congratulate you for the great work you are 
doing with the Xen Power PC porting.


 Let me introduce myself: my name is Mario Macías, from Barcelona 
Supercomputing Center ( http://www.bsc.es  ). We are 
absolutely interested in the usage of Xen for our research systems and, 
in the future, for production environment.


 Unfortunately, for the moment we cannot contribute with coding, but we 
expect to contribute to the improvement of Xen with our testing into 
research applications.


Best Regards,

Mario



P.S.:  I have noticed that now it's completed the SMP support. That's great!

--
Mario Macías Lloret

Barcelona Supercomputing Center research staff
Autonomic Computing and e-Business Platforms
[EMAIL PROTECTED]
Phone: +34 - 934134048

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

Re: [XenPPC] Introducing BSC

[XenPPC] [xenppc-unstable] [XEN][POWERPC] Linker script simplification broke optimized builds.

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

Re: [XenPPC] Introducing BSC

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

RE: [XenPPC] Changeset with 3 files on Friday (I think) has brokenXen on Mambo

[XenPPC] [xenppc-unstable] [XEN][POWERPC] fill in arch_vcpu_reset()

RE: [XenPPC] Build/config the world!

Re: [XenPPC] Changeset with 3 files on Friday (I think) has broken Xen on Mambo

Re: [XenPPC] Introducing BSC

[XenPPC] Build/config the world!

[XenPPC] Introducing BSC

12 matches

Site Navigation

Mail list logo

Footer information