WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] pciback.hide equivalent boot arg for PVOPS xen/master ke


On 12-Oct-2009, at 12:21 PM, Bruce Edge wrote:

On Mon, Oct 12, 2009 at 11:04 AM, McNeal, Rick <Rick.McNeal@xxxxxxx> wrote:
Have you used the /sys/bus/pci/drivers/pciback to do the same thing?

Here's what I tried:

These are devices I wanted to pass through:

lspci -n | grep 07:00

07:00.0 0c04: 11f8:8032 (rev 05)
07:00.1 0c04: 11f8:8032 (rev 05)
07:00.2 0c04: 11f8:8032 (rev 05)
07:00.3 0c04: 11f8:8032 (rev 05)

I started following the instructions for the pv_ops VT_d here:
http://wiki.xensource.com/xenwiki/VTdHowTo

0 #> echo "11f8 8032" > /sys/bus/pci/drivers/pci-stub/new_id
0 #> echo "0000:17:00.0" > /sys/bus/pci/devices/0000:17:00.0/driver/ unbind
0 #> echo "0000:17:00.0" > /sys/bus/pci/drivers/pci-stub/bind


On my system I would do the unbind first and then use new_slot instead of new_id. For example:

echo -n 0000:82:00.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:82:00.0 > /sys/bus/pci/drivers/pciback/bind

My current configuration doesn't require the unbind because no other driver is attempting to claim the device. I also noticed you're using pci-stub and not pciback. On my machine it doesn't have pci-stub. I'm currently running an older version of Xen than what I believe is current which might explain why thing are different and possibly working for me.

Then, when I ran

xm pci-attach dpm 0000:17:00.0 17      ( is that right? )


the console prints:

(XEN) [VT-D]iommu.c:1289:d0 domain_context_unmap:PCIe: bdf = 17:0.0
(XEN) [VT-D]iommu.c:1175:d0 domain_context_mapping:PCIe: bdf = 17:0.0
(XEN) [VT-D]iommu.c:1289:d0 domain_context_unmap:PCIe: bdf = 17:0.0
(XEN) [VT-D]iommu.c:1175:d0 domain_context_mapping:PCIe: bdf = 17:0.0

and the domU reboots.

-Bruce

----
Rick

Twenty years from now you will be more disappointed by the things you
didn't do than by the ones you did do. So throw off the bowline. Sail
away from the safe harbor. Catch the trade winds in your sails.
Explore. Dream. Discover. -Mark Twain

On Oct 12, 2009, at 11:26 AM, "Bruce Edge" <bruce.edge@xxxxxxxxx> wrote:

I used to be able to do this with the 2.6.30.3 dom0:
pciback.hide=(07:00.0)(07:00.1)(07:00.2)(07:00.3)(14:00.0)

Now I get:
Unknown boot option
`pciback.hide=(07:00.0)(07:00.1)(07:00.2)(07:00.3)(14:00.0)': ignoring

Is there an equivalent boot arg for the PVOPS kernel for this?

Where are the docs for what boot args this dom0 kernel supports?

-Bruce

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


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

----
Rick McNeal
rick.mcneal@xxxxxxx

"An armed society is a polite society. Manners are good when one may have to back up his acts with his life." -- Robert A. Heinlein



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