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: Fri, 31 Jul 2015 20:03:52 +0530
Message-ID: <55BB8750.5000707@caviumnetworks.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>	<55BB56E4.2030700@caviumnetworks.com>	<1438341549.30740.63.camel@citrix.com>	<55BB6F13.4080606@caviumnetworks.com>
	<55BB712B.1060402@citrix.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: <55BB712B.1060402@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: Julien Grall <julien.grall@citrix.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Prasun Kapoor <Prasun.kapoor@caviumnetworks.com>, "Kumar,
	Vijaya" <Vijaya.Kumar@caviumnetworks.com>, Stefano Stabellini <stefano.stabellini@citrix.com>, "Kulkarni,
	Ganapatrao" <Ganapatrao.Kulkarni@caviumnetworks.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hi Julien,

On 31/07/15 6:29 pm, Julien Grall wrote:
> Hi Manish,
>
> On 31/07/15 13:50, Manish Jaggi wrote:
>> Ok, i will implement the same from pciback to toolstack. I am not sure
>> about the complexity but will give it a try.
>> With this xen-pciback will not create the vdev-X entry at all.
> Can you send a new draft before continuing to implement PCI support in Xen?
I am working on the Draft 3 and addressing comments in draft 2. I am 
doing a feasibility of the stuff I put in draft3.
> As long as we are not agree about it,
I thought I was trying to discuss the same. If you have any point please 
raise it.
>   you loose your time trying to
> implement something that can drastically change in the next revision.
I am only putting the stuff in the Draft3 which *can* be implemented later.
Regards,