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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] abstract request_evtchn

To: Matt Chapman <matthewc@xxxxxx>
Subject: Re: [Xen-devel] [PATCH] abstract request_evtchn
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 2 Aug 2005 12:43:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Aug 2005 11:37:46 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050801223210.GA4532@xxxxxxxxxxxxxxx>
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>
References: <20050801223210.GA4532@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 1 Aug 2005, at 23:32, Matt Chapman wrote:

This patch provides request_evtchn and free_evtchn, intended
to be used instead of bind_evtchn_to_irq/request_irq and
free_irq/unbind_evtchn_from_irq.  This allows architectures
to implement event channels as they see fit, not necessarily
using Linux IRQs.

Why would you not hook into the IRQ subsystem? This doesn't seem like a useful patch to me.

 -- Keir

Xen-devel mailing list

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