Xen devel - Feb 2008 - bind_interdomain_evtchn_to_irqhandler and Xen 3.1

It appears that xen 3.2 has
''bind_interdomain_evtchn_to_irqhandler''...
if I wanted to convert some code back to 3.1, what call do I use
instead? There is a bind_evtchn_to_irqhandler, but that takes a
different number of parameters.

Thanks

James

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

Not sure what you mean? Isn''t that a kernel symbol? In which case it
has
nothing to do with a specific version of Xen itself.

 -- Keir

On 20/2/08 00:36, "James Harper" <james.harper@bendigoit.com.au>
wrote:
> It appears that xen 3.2 has
''bind_interdomain_evtchn_to_irqhandler''...
> if I wanted to convert some code back to 3.1, what call do I use
> instead? There is a bind_evtchn_to_irqhandler, but that takes a
> different number of parameters.
> 
> Thanks
> 
> James
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


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

> 
> Not sure what you mean? Isn''t that a kernel symbol? In which case
it
has
> nothing to do with a specific version of Xen itself.
> 
Yes. My bad. It''s a function that appears to have been introduced
sometime after 3.0.3 (which is around the level of the patches on the
Debian kernels).

I figured it out though. bind_interdomain_evtchn_to_irqhandler appears
to just be a helper function that does a EVTCHNOP_bind_interdomain
followed by a bind_evtchn_to_irqhandler.

The scsi passthrough backend now works against the Debian kernels (I
just compiled it out of tree) and I have written a windows PV frontend
driver for it - my tape drive is identified by windows, although if I
try a firmware upgrade on it it gets a bit upset, and I''m at a
different
location to the tape drive so I can''t put a tape in to test further.

James


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