From mboxrd@z Thu Jan  1 00:00:00 1970
From: Manish <mjaggi@caviumnetworks.com>
Subject: Re: [PATCH for-4.6 0/5] xen: arm: Parse PCI DT nodes'
 ranges and interrupt-map
Date: Thu, 19 Feb 2015 14:17:16 +0530
Message-ID: <54E5A314.80803@caviumnetworks.com>
References: <1414144694.15687.31.camel@citrix.com>	<54E168D6.6000502@amd.com>
	<54E1C2AA.3070504@linaro.org>	<54E2AFCC.3090302@amd.com>
	<54E34592.2020803@linaro.org>	<54E3472D.6030103@citrix.com>
	<54E3C21A.6080909@amd.com>	<54E3DD71.6070001@amd.com>
	<54E422FE.4080803@amd.com>	<54E48A0F.80900@linaro.org>
	<54E4F24E.2020602@amd.com>
	<54E5A97D020000780006182F@mail.emea.novell.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: <54E5A97D020000780006182F@mail.emea.novell.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: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org


On 19/02/15 1:44 pm, Jan Beulich wrote:
>>>> On 18.02.15 at 21:13, <suravee.suthikulpanit@amd.com> wrote:
>> On 2/18/2015 6:48 AM, Julien Grall wrote:
>>> Wouldn't it be possible to route the SPI dynamically when the domain
>>> decide to use the MSI n? We would need to implement PHYSDEVOP_map_pirq
>>> for MSI.
>> Enabling MSI is done by each end-point PCI device drivers in the guest.
>> In Linux, this would mean that when the driver tries to allocate an MSI
>> interrupt, it would need to communicate back to Xen (possibly via
>> hypercall as you pointed out) to get the next available SPI. It is not
>> necessary for now. I am planning to revisit this when we try to
>> implement pass-through support. Lemme know if you think this should be
>> handled differently.
> I think guest MSI setup should work at least similarly (if identically
> is not possible) to x86, i.e. via the vpci interface.
For cavium thunder pci passthrough, we have avoided that. Guest driver 
directly traps into hypervisor. No front end backend communication for 
MSI setup. The front-back communication is limited to reading PCI 
configuration space.
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel