Re: [XenPPC] [PATCH] Fix Maple SMP spurious interrupts assert

2006-10-13 Thread Jimi Xenidis 

I am not familiar with SMP spurious interrupts assert
   panic(Too many (%d) spurrious interrupts in a row\n
Known problem, please halt and let machine idle/ 
cool 

then reboot\n,
  100);
message?
That is independent of SMP, we get that in UP as well.
I'm willing to believe that this patch will make it so the panic does  
not happen.


On Oct 11, 2006, at 8:05 PM, Amos Waterland wrote:

This lets Xen with the SMP patch boot reliably on the Maple-D  
platform I

have access to.


Sure, I can even run one dom, but at some point my 405 either halts  
or resets the 970s

at seemingly random points.
I also get:
  PIBS $ Error: Magic number in message area NVRAM is not valid.
  Error: Magic number in message area NVRAM is not valid.
  Error: Magic number in message area NVRAM is not valid.

Which makes me a little woried that we have a wild write somewhere.



I believe that the long-term strategy for Xen/PPC is to completely
virtualize the PIC, but until that happens, this patch will I believe
allow the SMP patch to go in.


I send a suggestion for this patch.. I will attempt that as well.

-JX

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

Re: [XenPPC] [PATCH] Fix Maple SMP spurious interrupts assert

2006-10-12 Thread Jimi Xenidis 


On Oct 11, 2006, at 8:05 PM, Amos Waterland wrote:

This lets Xen with the SMP patch boot reliably on the Maple-D  
platform I

have access to.

I believe that the long-term strategy for Xen/PPC is to completely
virtualize the PIC, but until that happens, this patch will I believe
allow the SMP patch to go in.

Signed-off-by: Amos Waterland [EMAIL PROTECTED]


Wow, thats it?! this is good news, I'll have to verify it on my maple.
I think we can patch this better by copying:
  arch/powerpc/platforms/maple/setup.c maple_init_IRQ
into
  arch/powerpc/platforms/xen/evtchn.c

and simply drop:
  MPIC_WANTS_RESET
in the mpic_alloc() call.

and then have no changes in common code.

this make sense to you?
-JX

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