Good. The patch is reverting some functionality that I only understood quite
briefly. I think it's on devices that provide more than one function (e.g.
video 01:01.0 audio 01:01.1) and that in order to do a reset on one of them.
Somehow there is a restriction that all PCI devices that are behind one
bridge need to be assigned to the same domain. For consumer boards, nearly
all of them have all PCI slots behind one bridge. I am also not sure, whether
this is only for HVM, whereas we speak about PV here.
So I think it's a step back and I use the mentioned patch. All this PCI stuff
is quite nifty (and a major difference compared to other solutions), but I
haven't seen that much details on it from a pure user perspective (and for
REALY understanding hte code, I am too stupid).
One open question I have: is it realy necessary that PCI devices sharing a GSI
have to be co-assigned? (Just in case one of the gurus knows and will enlighten
us here ;o) )
BR,
Carsten-
----- Originalnachricht -----
Von: mdlabriola@xxxxxxxxx
Gesendet: Mit, 15.4.2009 14:30
An: Carsten Schiers <carsten@xxxxxxxxxx> ; xen-devel
<xen-devel@xxxxxxxxxxxxxxxxxxx>
Betreff: Re: AW: [Xen-devel] 3rd party drivers in domU or dom0
Yeah, that's the problem. I tried adding all the other mentioned PCI devices
to the domU as well, but then I got some other error message (I'm away from my
notebook right now). It was something about memory boundaries not aligning, if
memory serves...
-Mike
------Original Message------
From: Carsten Schiers
To: Michael Labriola
To: xen-devel
Subject: AW: [Xen-devel] 3rd party drivers in domU or dom0
Sent: Apr 15, 2009 08:19
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
---
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
|
Home