From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM Date: Mon, 6 Oct 2014 16:38:03 +0100 Message-ID: <1412609883.14255.18.camel@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: Anup Patel , Vijay Kilari , Prasun Kapoor , manish.jaggi@caviumnetworks.com, Julien Grall , xen-devel , psawargaonkar@linaro.org, Matt.Evans@arm.com, Dave.Martin@arm.com, manish jaggi List-Id: xen-devel@lists.xenproject.org On Mon, 2014-10-06 at 15:11 +0100, Stefano Stabellini wrote: > Actually the xen-pcifront driver in the guest knows the real PCI sbdf > for the assigned device, not just the virtual slot. On x86 xen-pcifront > makes an hypercall to enable msi/msix on the device passing the real > sbdf as argument: > > drivers/pci/xen-pcifront.c:pci_frontend_enable_msix > > Could we use the same hypercall to enable msi/msix on ARM? That would be > ideal. That's not a hypercall, it's a message to pciback. And I think it takes the virtual BDF, since pciback knows how to translate such things. > Otherwise xen-pcifront could call a new hypercall to let Xen know the > virtual sbdf to sbdf mapping. But I would prefer not to introduce a new > hypercall and reuse the existing one. Ian.