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

["Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>]

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