From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@citrix.com>
Subject: Re: PCI Pass-through in Xen ARM - Draft 2.
Date: Wed, 22 Jul 2015 09:34:09 +0100
Message-ID: <55AF5581.2070700@citrix.com>
References: <55903F12.7010908@caviumnetworks.com>
	<55911E66.2040009@citrix.com> <5598C6CD.2040207@caviumnetworks.com>
	<559A5BE4.1060707@citrix.com> <559A61FB.9070707@caviumnetworks.com>
	<559A6A4C.1090401@citrix.com> <559B7B4C.7080003@caviumnetworks.com>
	<559B8B64.9030800@citrix.com> <559B91DB.8030408@caviumnetworks.com>
	<1436268295.25646.162.camel@citrix.com>
	<559E1F0D.4050604@caviumnetworks.com> <559E2BFA.3050903@citrix.com>
	<alpine.DEB.2.02.1507141722460.17378@kaball.uk.xensource.com>
	<alpine.DEB.2.02.1507141742150.17378@kaball.uk.xensource.com>
	<55A53FB5.20906@citrix.com>
	<alpine.DEB.2.02.1507141805540.17378@kaball.uk.xensource.com>
	<55AF2D0C.9000704@caviumnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55AF2D0C.9000704@caviumnetworks.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>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>, Prasun Kapoor <Prasun.kapoor@caviumnetworks.com>, "Kumar,
	Vijaya" <Vijaya.Kumar@caviumnetworks.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Stefano Stabellini <stefano.stabellini@citrix.com>, "Kulkarni,
	Ganapatrao" <Ganapatrao.Kulkarni@caviumnetworks.com>
List-Id: xen-devel@lists.xenproject.org

Hi Manish,

On 22/07/2015 06:41, Manish Jaggi wrote:
> Can we keep this open and for now till there is agreement make
> requesterid = bdf.
> If you are ok, I will update and send Draft 3.

I think we can make an agreement on we are able to find a requesterID 
based on the BDF but not that requesterID = BDF. There is different 
reason for that: ARI, hardware quirks...

It would be nice if you can summarize how to find the requesterID, 
StreamIDs (SMMU), deviceID (IOMMU) and use the name accordingly in the spec.

Regards,

-- 
Julien Grall