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

[Xen-devel] RE: Please pull xen-ia64-unstable

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] RE: Please pull xen-ia64-unstable
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 8 Nov 2005 07:41:05 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 08 Nov 2005 15:41:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXkdYHNHn0o2XDMTpGelb/NtTvjpwABIlMg
Thread-topic: Please pull xen-ia64-unstable
Great, thanks!  Are these new interfaces checked into
xen-unstable yet?  I can't find the changeset. 

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
> Sent: Tuesday, November 08, 2005 8:08 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Please pull xen-ia64-unstable
> 
> 
> On 7 Nov 2005, at 18:45, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > Please pull
> >
> > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> >
> > Merged up thru xen-unstable cset 7642.
> 
> Okay, pulled through. I noticed that the event-channel 
> interfaces still 
> cause problems (bind_virq_to_irq in particular). I've had 
> another go at 
> rationalising the binding interface in light of this, so you now need 
> to implement:
>   bind_evtchn_to_irq --- same as it ever was
>   bind_virq_to_irqhandler --- replaces bind_virq_to_irq
>   bind_ipi_to_irqhandler --- replaces bind_ipi_to_irq
>   unbind_from_irqhandler --- common unbind function that replaces 
> unbind_evtchn_from_irqhandler, unbind_virq_from_irq and 
> unbind_ipi_from_irq
> 
> This interface eliminates all evtchn-related ia64 ifdefs in 
> common code.
> 
>   -- Keir
> 
> 

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

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