From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [RFC PATCH 00/19] xen/arm: Add ITS support Date: Fri, 13 Mar 2015 10:13:20 +0000 Message-ID: <5502B840.5040104@linaro.org> References: <1425299435-3278-1-git-send-email-vijay.kilari@gmail.com> <54F4635C.2050200@linaro.org> <54F59E59.4090204@linaro.org> <54FDE394.1010003@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Vijay Kilari Cc: Ian Campbell , Stefano Stabellini , Prasun Kapoor , Vijaya Kumar K , Tim Deegan , "xen-devel@lists.xen.org" , Stefano Stabellini , manish.jaggi@caviumnetworks.com List-Id: xen-devel@lists.xenproject.org Hi Vijay, On 13/03/2015 04:48, Vijay Kilari wrote: > The changes that I envisage for supporting Multiple ITS is > - Generate as many number of ITS dt nodes for Dom0 that host DT contains. > - For DomU always generate only one ITS node > - vITS will register MMIO handlers for all physical ITS of Dom0, but > vITS will only have > one VITS structure per domain. The limitation with this approach > is that all vITS requests are > serialized even though there are more than one physical ITS. But > this approach makes > implementation simple. Each vITS will have his own command queue... How do you plan to handle it with only a single structure? Can you provide an idea what the structure will look like? Regards, -- Julien Grall