AW: [Xen-devel] 3rd party drivers in domU or dom0

[Carsten Schiers <carsten@xxxxxxxxxx>]

Despite what Keir said on your timing requirements, I guess you get the famous
co-assignment message. See at the end of this:

http://www.nabble.com/xen-3.3.0-pv-pci-passthrough-co-assigned-problem-td20008460.html

BR,
Carsten.

----- Originalnachricht -----
Von: mdlabriola@xxxxxxxxx
Gesendet: Mit, 15.4.2009 13:56
An: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Betreff: [Xen-devel] 3rd party drivers in domU or dom0

I'm trying to use Xen 3.3.1 w/ the xen-linux mucurial kernel along with the 
Sabtech Swift PCI NTDS driver.  It's a 3rd party module that I have the source 
for, although I can't remember what the license says offhand (taints kernel as 
proprietary).

Basically I need either my dom0 or one of my domUs to be outputting NTDS data 
via 2 of these cards at 50 Hz each.  Initial tests have proven that the driver 
still works when compiled for dom0, but it's not quite meeting our timing 
requirements.  Most data is on time but we have a couple spikes over a 10 min 
run where 1 second's worth of data is taking around 1.03 seconds, if I remember 
correctly, and our spec only allows us to be .008 seconds late.

I tried to hide the PCI cards from dom0, to see what the behavior is like in a 
domU, but I can't get that to work either.  The pciback new_slot/bind stuff 
appears to work (I don't get errors), but when I try to create my domU, I get 
errors listing other devices that must also be sent to domU (looks like 
everything on that PCI bus)

Do you guys think there's a better chance of getting these boards working on 
domU or dom0?

-Mike

---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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