From mboxrd@z Thu Jan  1 00:00:00 1970
From: manish jaggi <manishjaggi.oss@gmail.com>
Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM
Date: Mon, 20 Oct 2014 19:00:49 +0530
Message-ID: <CAAiw7Jmq0zRHfv0VtyyFwJKzr5UsCd1wucSFDfY1d4xmisZ-zQ@mail.gmail.com>
References: <CAAiw7JnUfU1SQjnROrdNV0u2Z8_Fg68zkqJAh66Rwy9DB4LZsw@mail.gmail.com>
	<CAAiw7Jmg+p0--fFYcRnMDA2DdQ7Ss5zjH9iuLHeX=TpBPZYGbA@mail.gmail.com>
	<alpine.DEB.2.02.1410061452000.17038@kaball.uk.xensource.com>
	<CAAiw7JkOw=OQ5oBSO5jzcJt6eKhVTahzNkqeQ7p=qH_z-YCekg@mail.gmail.com>
	<alpine.DEB.2.02.1410071513060.17038@kaball.uk.xensource.com>
	<CAAiw7JkEvJsiqos1FY1TFKhBhQ=_Mmq297ZWH2xXDbpbe5MYcQ@mail.gmail.com>
	<20141008124657.GB13391@laptop.dumpdata.com>
	<CAAiw7JmG-+vxRDvnHNZ90JkdayFLy+ELkuA8u6S7BqCEB3dm5w@mail.gmail.com>
	<1412775916.24894.15.camel@citrix.com>
	<CAAiw7JmEZaMgk32g+0zgp=o-uD3dXUvQaCFwUv6HkUW+Pict5Q@mail.gmail.com>
	<20141008145107.GC18573@laptop.dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20141008145107.GC18573@laptop.dumpdata.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Julien Grall <julien.grall@linaro.org>, Ian Campbell <Ian.Campbell@citrix.com>, Vijay Kilari <vijay.kilari@gmail.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Prasun Kapoor <prasun.Kapoor@caviumnetworks.com>, manish.jaggi@caviumnetworks.com, Ryan Wilson <hap9@epoch.ncsc.mil>, xen-devel <xen-devel@lists.xen.org>, psawargaonkar@linaro.org, Anup Patel <anup.patel@linaro.org>
List-Id: xen-devel@lists.xenproject.org

On 8 October 2014 20:21, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Wed, Oct 08, 2014 at 07:17:48PM +0530, manish jaggi wrote:
>> On 8 October 2014 19:15, Ian Campbell <Ian.Campbell@citrix.com> 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?

Xen docs also mention about xen-pciback.passthrough=1. If I set this
in dom0 i see that the device is enumerated as the same sbdf in domU,
but
a) it is not shown in lspci
b) no front-back communication is done for reading devices configuration space
.
Is option useful / fully implemented for ARM ?