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-ppc-devel

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

To: Amos Waterland <apw@xxxxxxxxxx>
Subject: Re: [XenPPC] [PATCH] Fix Maple SMP spurious interrupts assert
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Thu, 12 Oct 2006 08:09:14 -0400
Cc: Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 12 Oct 2006 05:09:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061012000515.GA9842@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061012000515.GA9842@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx

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 <apw@xxxxxxxxxx>

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel

<Prev in Thread] Current Thread [Next in Thread>