From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: Xen/arm: Virtual ITS command queue handling
Date: Tue, 2 Jun 2015 09:29:46 +0100
Message-ID: <1433233786.15036.236.camel@citrix.com>
References: <CALicx6vrJquEdPY=VAHSEoMW5h2eJMgVA19sM+-_-W6vdX2TXQ@mail.gmail.com>
	<1431442942.8263.175.camel@citrix.com> <555239ED.2090400@citrix.com>
	<1431523416.8263.273.camel@citrix.com> <55535F30.7040903@citrix.com>
	<1431687548.8943.74.camel@citrix.com> <5555E46F.4010209@citrix.com>
	<1431694697.8943.119.camel@citrix.com> <5555F383.7030909@citrix.com>
	<1432037642.12989.106.camel@citrix.com> <555B3A5C.4090502@citrix.com>
	<1432042604.12989.124.camel@citrix.com>
	<1432043681.12989.135.camel@citrix.com>
	<CALicx6ufxg0Js1jHjQWidSX15na9KwbFSJ6suZatxrskLjPE8A@mail.gmail.com>
	<1432045085.12989.146.camel@citrix.com>
	<555DD19F.3060600@caviumnetworks.com>
	<1432645466.14664.107.camel@citrix.com>
	<556CE36F.2070301@caviumnetworks.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: <556CE36F.2070301@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>
Cc: Vijay Kilari <vijay.kilari@gmail.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>, manish.jaggi@caviumnetworks.com, Julien Grall <julien.grall@linaro.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Julien Grall <julien.grall@citrix.com>, Stefano Stabellini <stefano.stabellini@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, 2015-06-01 at 15:57 -0700, Manish Jaggi wrote:

> > Anyway, the general shape of this plan seems plausible enough.
> Could you modify the http://xenbits.xen.org/people/ianc/vits/draftC.html(5 vITS to pITS mapping) based on this approach

I'm updating things as I go and feed back will be relected in the next
draft.


> > > -5- domU is booted with a single virtual its node in device tree. Front 
> > > end driver  attaches this its as msi-parent
> > > -6- When domU accesses for ITS are trapped in Xen, using the helper 
> > > function say
> > > get_phys_its_for_guest(guest_id, guest_sbdf, /*[out]*/its_ptr *its)
> > > 
> > > its can be retrieved.
> > > AFAIK this is numa safe.
> > > > > 2) When PCI device is assigned to DomU, how does domU choose
> > > > >      vITS to send commands.  AFAIK, the BDF of assigned device
> > > > >      is different from actual BDF in DomU.
> > > > AIUI this is described in the firmware tables.
> > > > 
> > > > e.g. in DT via the msi-parent phandle on the PCI root complex or
> > > > individual device.
> > > > 
> > > > Is there an assumption here that a single PCI root bridge is associated
> > > > with a single ITS block? Or can different devices on a PCI bus use
> > > > different ITS blocks?
> > > > 
> > > > Ian.
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@lists.xen.org
> > > > http://lists.xen.org/xen-devel
> > 
>