|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH PV_OPS PCIFRONT]
On 11/05/09 14:04, Konrad Rzeszutek Wilk wrote:
>> That is it for right now. The driver works with INTx and MSI cards. I've
>> tested
>> with USB and network (Broadcom) succesfully. There is still some more work
>> to do:
>> - MSI disable is not yet in,
>> - no MSI-X enable/disable functionality.
>>
> and:
> - If 4GB or more are allocated to the domain, you get this:
>
> PCI: Warning: Cannot find a gap in the 32bit address range
> PCI: Unassigned devices with 32bit resource registers may break!
>
> and the device shows up as disabled and is not usuable.
>
Presumably less than 4G can trigger this. My rough thought about this
was to always reserve a chunk of memory under 4G to make space for this
kind of thing, and push the displaced memory higher.
> - No support yet for 'reassign_device' which page aligns the BARs
> on PCI devices.
>
> - Haven't tested FLR or PCI AER.
> - Saw this once:
>
> WARNING: at drivers/pci/msi.c:602 pci_enable_msi_block+0xcd/0x339()
> .. snip ..
> Call Trace:
> [<ffffffff8107ed59>] warn_slowpath_common+0xc9/0x10c
> [<ffffffff8107edcc>] warn_slowpath_null+0x30/0x4d
> [<ffffffff81362cec>] pci_enable_msi_block+0xcd/0x339
> [<ffffffff814006ec>] ? pciback_do_op+0x0/0x1b4
> [<ffffffff8140469e>] pciback_enable_msi+0x3e/0xb0
> [<ffffffff814007b9>] pciback_do_op+0xcd/0x1b4
> ..snip..
>
What does that warning mean?
> But besides that it works :-)
>
Good! I'll throw it into the mix and see how it flies.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|