Re: 3rd party drivers in domU or dom0

Re: 3rd party drivers in domU or dom0

[mdlabriola]

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

I booted the hypervizor with dom0_vcpu_pin set, dom0's kernel with nosmp set, then pinned my domUs to the second core.  It worked!  I'm now sending my 50Hz data well within my spec, even with two other domUs working away.  :-)

Now, I still would rather pass my PCI cards into a domU, but I'm pretty happy to be working at all.

I remember noticing an option to select one of 3 available PCI passthrough methods for pciback when I configured my kernel...  What's the difference between the three?

-Mike

------Original Message------
From: Keir Fraser
To: Michael Labriola
To: xen-devel
Subject: Re: [Xen-devel] 3rd party drivers in domU or dom0
Sent: Apr 15, 2009 08:01

On 15/04/2009 12:56, "mdlabriola@yahoo.com" <mdlabriola@yahoo.com> wrote:

> 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?

Doesn't matter which as Xen schedules them the same. The safest way would be
to run a uniproc dom0 or domU, and dedicate a cpu to it (by setting affinity
masks of all domains).

 -- Keir





---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: 3rd party drivers in domU or dom0

[Keir Fraser]

On 15/04/2009 12:56, "mdlabriola@yahoo.com" <mdlabriola@yahoo.com> wrote:

> 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?

Doesn't matter which as Xen schedules them the same. The safest way would be
to run a uniproc dom0 or domU, and dedicate a cpu to it (by setting affinity
masks of all domains).

 -- Keir

3rd party drivers in domU or dom0

[mdlabriola]

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

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

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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