From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM Date: Wed, 8 Oct 2014 10:51:07 -0400 Message-ID: <20141008145107.GC18573@laptop.dumpdata.com> References: <20141008124657.GB13391@laptop.dumpdata.com> <1412775916.24894.15.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline 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: manish jaggi Cc: Julien Grall , Ian Campbell , Vijay Kilari , Stefano Stabellini , Prasun Kapoor , manish.jaggi@caviumnetworks.com, Ryan Wilson , xen-devel , psawargaonkar@linaro.org, Anup Patel List-Id: xen-devel@lists.xenproject.org On Wed, Oct 08, 2014 at 07:17:48PM +0530, manish jaggi wrote: > On 8 October 2014 19:15, Ian Campbell wrote: > > On Wed, 2014-10-08 at 19:07 +0530, manish jaggi wrote: > >> Thanks for replying. As detailed in this thread, I need to create a > >> hypercall that would send the following information to Xen at the time > >> of PCI attach > >> { sbdf , domU sbdf, domainId }. > >> I am not able to find a way to get the domU sbdf from dom0 at the time > >> of pci-attach. > > > > I think it would need to be done by the pciback driver in the dom0 > > kernel, which AFAIK is the thing which consistently knows both physical > > and virtual sbdf for a given assigned device. > > > > Ian. > > > Correct, can you point out which data structure holds the domU sbdf > corresponding to the actual sbdf in pciback. See 'xen_pcibk_export_device' or 'xen_pcibk_publish_pci_root' is that what you are referring to?