From mboxrd@z Thu Jan  1 00:00:00 1970
From: Manish Jaggi <mjaggi@caviumnetworks.com>
Subject: Re: PCI Pass-through in Xen ARM - Draft 2.
Date: Wed, 22 Jul 2015 11:11:32 +0530
Message-ID: <55AF2D0C.9000704@caviumnetworks.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>
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: <alpine.DEB.2.02.1507141805540.17378@kaball.uk.xensource.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: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Julien Grall <julien.grall@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



On Tuesday 14 July 2015 11:31 PM, Stefano Stabellini wrote:
> On Tue, 14 Jul 2015, Julien Grall wrote:
>> Hi Stefano,
>>
>> On 14/07/2015 18:46, Stefano Stabellini wrote:
>>>>> Linux provides a function (pci_for_each_dma_alias) which will return a
>>>>> requester ID for a given PCI device. It appears that the BDF (the 's' of
>>>>> sBDF
>>>>> is only internal to Linux and not part of the hardware) is equal to the
>>>>> requester ID on your platform but we can't assume it for anyone else.
>>>> The PCI Express Base Specification states that the requester ID is "The
>>>> combination of a Requester's Bus Number, Device Number, and Function
>>>> Number that uniquely identifies the Requester."
>>>>
>>>> I think it is safe to assume BDF = requester ID on all platforms.
>>> With the catch that in case of ARI devices
>>> (http://pcisig.com/sites/default/files/specification_documents/ECN-alt-rid-interpretation-070604.pdf),
>>> BDF is actually BF because the device number is always 0 and the
>>> function number is 8 bits.
>> And some other problem such as broken PCI device...
>> Both Xen x86 (domain_context_mapping in drivers/passthrough/vtd/iommu.c) and
>> Linux (pci_dma_for_each_alias) use a code more complex than requesterID = BDF.
>>
>> So I don't think we can use requesterID = BDF in physdev op unless we are
>> *stricly* sure this is valid.
> The spec is quite clear about it, but I guess there might be hardware quirks.
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.
>
>
>> Although, based on the x86 code, Xen should be able to translate the BDF into
>> the requester ID...
> Yes, that is a good point.