Re: [Xen-devel] [PATCH PV_OPS] pciback support

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Hello Konrad,

With the 2.6.18.8 kernel and 2.6.29.6 port of the xen kernel (on xen 3.4.1 
hypervisor)
I had to use an additional guestdev= and reassign_resources to make things work.

Are these also ported/available on the 2.6.31.1/pv_ops kernel or not needed 
anymore ?

Complete lines in grub dom0:

kernel          /xen-3.4.1.gz dom0_mem=768M xencons=hvc
module          /vmlinuz-2.6.29.6 root=/dev/mapper/serveerstertje-root ro 
pci=nomsi 
pciback.hide=(00:07.0)(06:01.0)(06:01.1)(06:01.2)(01:08.0)(01:08.1)(01:08.2)(01:0a.0)
  guestdev=00:07.0,06:01.0,06:01.1,06:01.2,01:08.0,01:08.1,01:08.2,01:0a.0 
reassign_resources swiotlb=256,force console=tty0
module          /initrd.img-2.6.29.6

making this work for me by passing through 2 USB cards (one pci one pci-e) and 
a integrated intel hda sound card) to domU's


Regards,

Sander Eikelenboom




Tuesday, October 13, 2009, 11:22:19 PM, you wrote:

> This is back-port (up-port?) of the pci-back driver from the 2.6.18.hg tree.
> The driver is quite similar to the pci-stub, excep that is intended for
> paravirtualized guests. This driver works in conjunction with the pci-front
> (frontend driver) to exchange PCI write/read to the configuration space and
> to have the BARs mapped properly for the guest.

> The usage of this is, as said, is similar to pci-stub:
> lspci | grep SCSI
> 01:14.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
> echo "0000:01:14.0" > /sys/bus/pci/drivers/aic94xx/unbind
> echo "0000:01:14.0" > /sys/bus/pci/drivers/pciback/new-slot
> echo "0000:01:14.0" > /sys/bus/pci/drivers/aic94xx/bind

> and add this entry:

> pci = [ '0000:01.14.0' ]

> in your .xm file.

> The PV guest, if it has the PCI frontend, should now see the PCI device.
> I've tested this succesfully with a SLES10 PV guest with a couple of devices.

> But please be beware of this warning if it shows up:
> (XEN) irq.c:1113:d1 Cannot bind IRQ 17 to guest. Others do not share.

> On my machine it lead to Dom0 deciding that a spurrious interrupt kicked off
> and it disabled the IRQ. The end result was that other devices on the same
> interrupt line stopped working. I am not yet certain how to make this work
> properly (whether to check if the PCI device in question interrupt line is
> being shared beforehand by xm?, or do something in Xen?).







-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


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