From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@citrix.com>
Subject: Re: [PATCH v5 21/22] xen/arm: ITS: Generate ITS node
 for Dom0
Date: Fri, 21 Aug 2015 16:48:01 -0700
Message-ID: <55D7B8B1.1000206@citrix.com>
References: <1437995524-19772-1-git-send-email-vijay.kilari@gmail.com>
	<1437995524-19772-22-git-send-email-vijay.kilari@gmail.com>
	<55D238CC.2060904@citrix.com>
	<CALicx6u3_eU=jjcm=p=U-BfrVzqbh6YEDfP6+XUY-rfwg=D+6Q@mail.gmail.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: <CALicx6u3_eU=jjcm=p=U-BfrVzqbh6YEDfP6+XUY-rfwg=D+6Q@mail.gmail.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: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>, manish.jaggi@caviumnetworks.com, Tim Deegan <tim@xen.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Stefano Stabellini <stefano.stabellini@citrix.com>, Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
List-Id: xen-devel@lists.xenproject.org



On 21/08/2015 16:02, Vijay Kilari wrote:
> On Mon, Aug 17, 2015 at 12:41 PM, Julien Grall <julien.grall@citrix.com> wrote:
>>
>>
>> On 27/07/2015 04:12, vijay.kilari@gmail.com wrote:
>>>
>>> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>>>
>>> Parse host dt and generate ITS node for Dom0.
>>> ITS node resides inside GIC node so when GIC node
>>> is encountered look for ITS node.
>>>
>>> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>>> ---
>>> v5: - Moved ITS dt node generation to ITS driver
>>> v4: - Generate only one ITS node for Dom0
>>>       - Replace msi-parent references to single its phandle
>>> ---
>>>    xen/arch/arm/domain_build.c   |   17 ++++++++++
>>>    xen/arch/arm/gic-v3-its.c     |   74
>>> +++++++++++++++++++++++++++++++++++++++++
>>>    xen/arch/arm/gic-v3.c         |   29 ++++++++++++++++
>>>    xen/arch/arm/gic.c            |   18 ++++++++++
>>>    xen/include/asm-arm/gic-its.h |    3 ++
>>>    xen/include/asm-arm/gic.h     |    7 ++++
>>>    6 files changed, 148 insertions(+)
>>>
> [...]
>>> +static int gicv3_make_hwdom_its_dt_node(const struct domain *d,
>>> +                                        const struct dt_device_node
>>> *node,
>>> +                                        void *fdt)
>>> +{
>>> +    struct dt_device_node *gic_child;
>>> +    int res = 0;
>>> +
>>> +    static const struct dt_device_match its_matches[] __initconst =
>>> +    {
>>> +        DT_MATCH_GIC_ITS,
>>> +        { /* sentinel */ },
>>> +    };
>>> +
>>> +    dt_for_each_child_node(node, gic_child)
>>> +    {
>>> +        if ( gic_child != NULL )
>>> +        {
>>> +            if ( dt_match_node(its_matches, gic_child) )
>>> +            {
>>> +                res = its_make_dt_node(d, gic_child, fdt);
>>> +                break;
>>> +            }
>>> +        }
>>> +    }
>>
>>
>> I already asked on v4, why do you need this loop? The GIC node for the DOM0
>> is recreating from scratch, there is no need of looping on the current GIC
>> node...
>
>    It ensures that ITS node for Dom0 is generated only if dt_host has it.

That's wrong. The ITS node maybe be present in the DT but the ITS driver 
never initialized. Furthermore, we may decide at some point to not 
exposed the ITS to DOM0.

You should introduced a variable to know whether the ITS is used for 
DOM0 or not and not relying on the hw DT. This is pointless and make the 
code harder to read.

Regards,

-- 
Julien Grall