From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: iommu=dom0-passthrough behavior Date: Fri, 16 Nov 2012 09:26:28 +0000 Message-ID: <50A614D402000078000A9240@nat28.tlf.novell.com> References: <5097DB9102000078000A65C7@nat28.tlf.novell.com> <50A20DE302000078000A7F6B@nat28.tlf.novell.com> <50A223DE02000078000A7FE6@nat28.tlf.novell.com> <50A23C0C02000078000A8085@nat28.tlf.novell.com> <50A2755402000078000A837D@nat28.tlf.novell.com> <50A3AD4E02000078000A87BD@nat28.tlf.novell.com> <50A4BE6D02000078000A8B89@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Xiantao Zhang , Yang Z Zhang Cc: "wei.huang2@amd.com" , "weiwang.dd@gmail.com" , xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 16.11.12 at 07:21, "Zhang, Xiantao" wrote: > Okay. Back to your customer's issue, I don't think we have a clean solution > if the device can't be detected by hypervisor. We only can figure out how > to workaround this issue through a new command line option. 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? Jan