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>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] abstract request_evtchn
From: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>
Date: Wed, 3 Aug 2005 23:09:48 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Aug 2005 15:08:22 +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: AcWXoIxAlZF56+NpSV+rYqutjdprMwAnGbMg
Thread-topic: [Xen-devel] [PATCH] abstract request_evtchn

Matt Chapman <> wrote:
> On Tue, Aug 02, 2005 at 12:43:43PM +0100, Keir Fraser wrote:
> I'm trying to keep all the Xen drivers and related infrastructure in
> modules - IMHO domains that aren't paravirtualised should be able to
> use the optimised drivers too, plus it makes development easier.  
> irq_desc isn't exported from the Linux kernel on most architectures,
> so I'm not sure how one would "hook into" the IRQ subsystem in that
> way from a module.  Also, this limits the number of event channels to
> NR_IRQS (minus the ones that are used in other ways).  Instead I have
> the event channel subsystem register for a single IRQ and then
> demultiplex internally (in the way that is already done by
> evtchn_do_upcall).      

Yes, currently, when I make a frontend driver to module in unmodified 
vmx domain, I need to change request_irq to xen_request_irq, and 
use a seperate irq spaced for these para-driver.
if frontend driver use request_evtchn, then I don't need the change
and just implement a new request_evtchn(),

Xen-devel mailing list

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