[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] PCI delegation works, access to the delegated NIC doesn't

> To this end I've checked in a 'permissive' module flag which allows PCI
> config writes to succeed by default. Enabled by specifying
> 'pciback.permissive' as a boot parameter or:
>   echo Y >/sys/modules/pciback/permissive
>   -- Keir

Hi Keir, hi Ryan,

good job! I recompiled with the mentioned changeset and it works.
At the moment I'm writing this mail from my dom0 via a bridge created with the 
delegated NIC. Thank's a lot.

I just had one issue with a kernel oops when I set up the bridge in domU

brctl addbr br0
brctl addif eth0 (the vif)
brctl addif eth1 (the delegated NIC)

ifconfig br0 up


Aiee, killing interrupt....

Unfortunately I was not able to catch the output, because the domU crashed 

But this is what I could get from dom0's dmesg after crash:


ACPI: PCI interrupt for device 0000:02:00.0 disabled
irq 16: nobody cared (try booting with the "irqpoll" option)

Call Trace: <IRQ> <ffffffff8010722a>{hypercall_page+554}
       <ffffffff80274b3a>{usb_hcd_irq+42} <ffffffff80151f66>{__do_IRQ+214}
       <ffffffff8010dee8>{do_IRQ+72} <ffffffff8025be55>{evtchn_do_upcall+149}
       <ffffffff8010bb19>{do_hypervisor_callback+37} <EOI>
[<ffffffff80274b10>] (usb_hcd_irq+0x0/0x60)
Disabling IRQ #16


After that it was also not possible to reboot the domU, so I had to reboot 
dom0 as well.

But this happened only once, after rebooting I couldn't reproduce that oops 
anymore. Will do further tests later.

What about the info's requested by you before that permissive-patch? Are they 
still of interest?
I did those tests before I recompiled, so if needed I can still attach them to 
the bugzilla report.

Thanks again,

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.