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

Re: [Xen-devel] iommu=dom0-passthrough behavior

>>> On 16.11.12 at 10:43, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx> wrote:
>>  So after I implemented a draft patch for this yesterday, my attention now
>> was directed to phantom functions permitted by the PCIe spec (of which I
>> was entirely unaware so far). While Linux to date doesn't enable them, I 
> can't
>> exclude that the BIOS might be (requested respective data to find out). And
>> even if it doesn't, adding proper support for that functionality, and then
>> putting a quirk on top of that would seem the much cleaner solution (pretty
>> likely me_wifi_quirk() could then also be made fit in there).
>> Thoughts?
> Agree, Xen doesn't have phantom functions supported with VT-d, so it is  
> better to create a quirk to fix such issues.  

Sorry, no, we should add phantom function support (and not
only to VT-d, but to the generic IOMMU code), and use that (if
necessary, i.e. if the device in question doesn't have phantom
functions turned on) to base a workaround on.


Xen-devel mailing list



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