From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: PCI Pass-through in Xen ARM - Draft 2.
Date: Fri, 31 Jul 2015 11:32:19 +0100
Message-ID: <1438338739.30740.55.camel@citrix.com>
References: <55903F12.7010908@caviumnetworks.com>
	<55911E66.2040009@citrix.com> <5598C6CD.2040207@caviumnetworks.com>
	<1436173886.25646.24.camel@citrix.com>	<559A532F.50305@caviumnetworks.com>
	<1436178036.25646.28.camel@citrix.com>
	<55B89ED5.4040904@caviumnetworks.com>
	<1438250078.11600.272.camel@citrix.com>
	<55BA1DB5.7090102@caviumnetworks.com>
	<1438267154.11600.357.camel@citrix.com>
	<55BB27DF.2090509@caviumnetworks.com>
	<1438329920.30740.14.camel@citrix.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: <1438329920.30740.14.camel@citrix.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: Manish Jaggi <mjaggi@caviumnetworks.com>
Cc: Prasun Kapoor <Prasun.kapoor@caviumnetworks.com>, "Kumar,
	Vijaya" <Vijaya.Kumar@caviumnetworks.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Julien Grall <julien.grall@citrix.com>, Stefano Stabellini <stefano.stabellini@citrix.com>, "Kulkarni,
	Ganapatrao" <Ganapatrao.Kulkarni@caviumnetworks.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, 2015-07-31 at 09:05 +0100, Ian Campbell wrote:
> On Fri, 2015-07-31 at 13:16 +0530, Manish Jaggi wrote:
> > > > Secondly, the vdev-X entry is created async by dom0 watching on 
> > > > event.

Stefano points out that there are, confusingly, two nodes in xenstore
relating to the virtual-SBDF.

vdev-X is written by pciback and is read by pcifront, it is effectively
there to communicate the vSBDF to the guest.

vdevfn-X is written by the toolstack (libxl_create_pci_backend_device) to
tell the backend (pciback, or qemu in x86/HVM configurations using old
qemu) the vSBDF to be associated with the device.

It looks like vdevfn-X is not actually currently supported by pciback in
Linux (seemingly only the x86/HVM qemu backend consumes it). I think we
should add that support to pciback for consistency with the qemu based
backend used by x86/HVM guests.

The names are a certainly a bit confusing. We could add a new key with a
better name to communicate the vSBDF from toolstack->backend, but itseems
to me to be that would just adding even more confusion, so I recommend we
don't do that.

Once pciback supports vdevfn then libxl will be able to choose the PCI bus
layout for ARM guests in the case where the use has not requested an
explicit vdevfn for the device.

Does that make sense?

Ian.