All of lore.kernel.org
 help / color / mirror / Atom feed
From: thunder.leizhen@huawei.com (Leizhen (ThunderTown))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] of/numa: fix a memory@ dt node can only contains one memory block
Date: Fri, 27 May 2016 15:04:11 +0800	[thread overview]
Message-ID: <5747F16B.5050404@huawei.com> (raw)
In-Reply-To: <CAL_JsqJXu36qYMOZeWDnMQ8BnOxMrixv5N70hvTjDixhMCQKRw@mail.gmail.com>



On 2016/5/27 12:20, Rob Herring wrote:
> On Thu, May 26, 2016 at 10:36 PM, Leizhen (ThunderTown)
> <thunder.leizhen@huawei.com> wrote:
>>
>>
>> On 2016/5/26 21:13, Rob Herring wrote:
>>> On Thu, May 26, 2016 at 10:43:58AM +0800, Zhen Lei wrote:
>>>> For a normal memory@ devicetree node, its reg property can contains more
>>>> memory blocks.
>>>>
>>>> Because we don't known how many memory blocks maybe contained, so we try
>>>> from index=0, increase 1 until error returned(the end).
>>>>
>>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>>> ---
>>>>  drivers/of/of_numa.c | 30 ++++++++++++++++++++----------
>>>>  1 file changed, 20 insertions(+), 10 deletions(-)
>>>>
>>>> diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
>>>> index 21d831f..2c5f249 100644
>>>> --- a/drivers/of/of_numa.c
>>>> +++ b/drivers/of/of_numa.c
>>>> @@ -63,7 +63,7 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>      struct device_node *np = NULL;
>>>>      struct resource rsrc;
>>>>      u32 nid;
>>>> -    int r = 0;
>>>> +    int i, r = 0;
>>>>
>>>>      for (;;) {
>>>>              np = of_find_node_by_type(np, "memory");
>>>> @@ -82,17 +82,27 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>                      /* some other error */
>>>>                      break;
>>>>
>>>> -            r = of_address_to_resource(np, 0, &rsrc);
>>>> -            if (r) {
>>>> -                    pr_err("NUMA: bad reg property in memory node\n");
>>>> -                    break;
>>>> +            for (i = 0; ; i++) {
>>>> +                    r = of_address_to_resource(np, i, &rsrc);
>>>> +                    if (r) {
>>>> +                            /* reached the end of of_address */
>>>> +                            if (i > 0) {
>>>> +                                    r = 0;
>>>> +                                    break;
>>>> +                            }
>>>> +
>>>> +                            pr_err("NUMA: bad reg property in memory node\n");
>>>> +                            goto finished;
>>>> +                    }
>>>> +
>>>> +                    r = numa_add_memblk(nid, rsrc.start,
>>>> +                                        rsrc.end - rsrc.start + 1);
>>>> +                    if (r)
>>>> +                            goto finished;
>>>>              }
>>>> -
>>>> -            r = numa_add_memblk(nid, rsrc.start,
>>>> -                                rsrc.end - rsrc.start + 1);
>>>> -            if (r)
>>>> -                    break;
>>>>      }
>>>> +
>>>> +finished:
>>>>      of_node_put(np);
>>>
>>> This function can be simplified down to:
>>>
>>>       for_each_node_by_type(np, "memory") {
>> OK, That's good.
>>
>>>               r = of_property_read_u32(np, "numa-node-id", &nid);
>>>               if (r == -EINVAL)
>>>                       /*
>>>                        * property doesn't exist if -EINVAL, continue
>>>                        * looking for more memory nodes with
>>>                        * "numa-node-id" property
>>>                        */
>>>                       continue;
>> Hi, everybody:
>>     If some "memory" node contains "numa-node-id", but some others missed. Can we simply ignored it?
>> I think we should break out too, and faking to only have node0.
> 
> Continuing to work is probably better than not.
> 
>>
>>>               else if (r)
>>>                       /* some other error */
>>>                       break;
>>>
>>>               r = of_address_to_resource(np, 0, &rsrc);
>>>               for (i = 0; !r; i++, r = of_address_to_resource(np, i,
>>
>> But r(non-zero) is just break this loop, the original is break the outer for (;;) loop
> 
> It is not really the kernel's job to validate the DT. If there's
> random things in it then kernel's behavior is undefined.
> 
>>
>> How about as below?
>>
>>         for_each_node_by_type(np, "memory") {
>>                 ... ...
>>
>>                 for (i = 0; !of_address_to_resource(np, i, &rsrc); i++) {
>>                         r = numa_add_memblk(nid, rsrc.start,
>>                                             rsrc.end - rsrc.start + 1);
>>                         if (r)
>>                                 goto finished;
>>                 }
>>
>>                 if (!i)
>>                         pr_err("NUMA: bad reg property in memory node\n");
>>         }
>>
>> finished:
> 
> Please try to avoid the goto. You can check r in the outer loop too.

OK. I have rewritten this function according to your advice.

	for_each_node_by_type(np, "memory") {
                r = of_property_read_u32(np, "numa-node-id", &nid);
                if (r == -EINVAL)
                        /*
                         * property doesn't exist if -EINVAL, continue
                         * looking for more memory nodes with
                         * "numa-node-id" property
                         */
                        continue;
									//I deleted the break of "some other error", and it will break in below "if (!i || r)" branch

                for (i = 0; !r && !of_address_to_resource(np, i, &rsrc); i++)
                        r = numa_add_memblk(nid, rsrc.start,
                                            rsrc.end - rsrc.start + 1);

                if (!i || r) {
                        of_node_put(np);				//I moved here, so that it looks more clear. Because in the normal use of for_each_node_by_type, of_node_put is not required
                        pr_err("NUMA: bad property in memory node\n");	//Deleted "reg", so that it's suitable or harmless for other error cases
                        break;
                }
        }

	return r;

> 
> Rob
> 
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Leizhen (ThunderTown)" <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	Ganapatrao Kulkarni
	<gkulkarni-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
	Robert Richter <rrichter-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
	David Daney <david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
	Frank Rowand
	<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Grant Likely
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Xinwei Hu <huxinwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Tianhong Ding
	<dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Hanjun Guo <guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 2/3] of/numa: fix a memory@ dt node can only contains one memory block
Date: Fri, 27 May 2016 15:04:11 +0800	[thread overview]
Message-ID: <5747F16B.5050404@huawei.com> (raw)
In-Reply-To: <CAL_JsqJXu36qYMOZeWDnMQ8BnOxMrixv5N70hvTjDixhMCQKRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>



On 2016/5/27 12:20, Rob Herring wrote:
> On Thu, May 26, 2016 at 10:36 PM, Leizhen (ThunderTown)
> <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> wrote:
>>
>>
>> On 2016/5/26 21:13, Rob Herring wrote:
>>> On Thu, May 26, 2016 at 10:43:58AM +0800, Zhen Lei wrote:
>>>> For a normal memory@ devicetree node, its reg property can contains more
>>>> memory blocks.
>>>>
>>>> Because we don't known how many memory blocks maybe contained, so we try
>>>> from index=0, increase 1 until error returned(the end).
>>>>
>>>> Signed-off-by: Zhen Lei <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>>>> ---
>>>>  drivers/of/of_numa.c | 30 ++++++++++++++++++++----------
>>>>  1 file changed, 20 insertions(+), 10 deletions(-)
>>>>
>>>> diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
>>>> index 21d831f..2c5f249 100644
>>>> --- a/drivers/of/of_numa.c
>>>> +++ b/drivers/of/of_numa.c
>>>> @@ -63,7 +63,7 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>      struct device_node *np = NULL;
>>>>      struct resource rsrc;
>>>>      u32 nid;
>>>> -    int r = 0;
>>>> +    int i, r = 0;
>>>>
>>>>      for (;;) {
>>>>              np = of_find_node_by_type(np, "memory");
>>>> @@ -82,17 +82,27 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>                      /* some other error */
>>>>                      break;
>>>>
>>>> -            r = of_address_to_resource(np, 0, &rsrc);
>>>> -            if (r) {
>>>> -                    pr_err("NUMA: bad reg property in memory node\n");
>>>> -                    break;
>>>> +            for (i = 0; ; i++) {
>>>> +                    r = of_address_to_resource(np, i, &rsrc);
>>>> +                    if (r) {
>>>> +                            /* reached the end of of_address */
>>>> +                            if (i > 0) {
>>>> +                                    r = 0;
>>>> +                                    break;
>>>> +                            }
>>>> +
>>>> +                            pr_err("NUMA: bad reg property in memory node\n");
>>>> +                            goto finished;
>>>> +                    }
>>>> +
>>>> +                    r = numa_add_memblk(nid, rsrc.start,
>>>> +                                        rsrc.end - rsrc.start + 1);
>>>> +                    if (r)
>>>> +                            goto finished;
>>>>              }
>>>> -
>>>> -            r = numa_add_memblk(nid, rsrc.start,
>>>> -                                rsrc.end - rsrc.start + 1);
>>>> -            if (r)
>>>> -                    break;
>>>>      }
>>>> +
>>>> +finished:
>>>>      of_node_put(np);
>>>
>>> This function can be simplified down to:
>>>
>>>       for_each_node_by_type(np, "memory") {
>> OK, That's good.
>>
>>>               r = of_property_read_u32(np, "numa-node-id", &nid);
>>>               if (r == -EINVAL)
>>>                       /*
>>>                        * property doesn't exist if -EINVAL, continue
>>>                        * looking for more memory nodes with
>>>                        * "numa-node-id" property
>>>                        */
>>>                       continue;
>> Hi, everybody:
>>     If some "memory" node contains "numa-node-id", but some others missed. Can we simply ignored it?
>> I think we should break out too, and faking to only have node0.
> 
> Continuing to work is probably better than not.
> 
>>
>>>               else if (r)
>>>                       /* some other error */
>>>                       break;
>>>
>>>               r = of_address_to_resource(np, 0, &rsrc);
>>>               for (i = 0; !r; i++, r = of_address_to_resource(np, i,
>>
>> But r(non-zero) is just break this loop, the original is break the outer for (;;) loop
> 
> It is not really the kernel's job to validate the DT. If there's
> random things in it then kernel's behavior is undefined.
> 
>>
>> How about as below?
>>
>>         for_each_node_by_type(np, "memory") {
>>                 ... ...
>>
>>                 for (i = 0; !of_address_to_resource(np, i, &rsrc); i++) {
>>                         r = numa_add_memblk(nid, rsrc.start,
>>                                             rsrc.end - rsrc.start + 1);
>>                         if (r)
>>                                 goto finished;
>>                 }
>>
>>                 if (!i)
>>                         pr_err("NUMA: bad reg property in memory node\n");
>>         }
>>
>> finished:
> 
> Please try to avoid the goto. You can check r in the outer loop too.

OK. I have rewritten this function according to your advice.

	for_each_node_by_type(np, "memory") {
                r = of_property_read_u32(np, "numa-node-id", &nid);
                if (r == -EINVAL)
                        /*
                         * property doesn't exist if -EINVAL, continue
                         * looking for more memory nodes with
                         * "numa-node-id" property
                         */
                        continue;
									//I deleted the break of "some other error", and it will break in below "if (!i || r)" branch

                for (i = 0; !r && !of_address_to_resource(np, i, &rsrc); i++)
                        r = numa_add_memblk(nid, rsrc.start,
                                            rsrc.end - rsrc.start + 1);

                if (!i || r) {
                        of_node_put(np);				//I moved here, so that it looks more clear. Because in the normal use of for_each_node_by_type, of_node_put is not required
                        pr_err("NUMA: bad property in memory node\n");	//Deleted "reg", so that it's suitable or harmless for other error cases
                        break;
                }
        }

	return r;

> 
> Rob
> 
> .
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Rob Herring <robh@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
	Robert Richter <rrichter@cavium.com>,
	"David Daney" <david.daney@cavium.com>,
	Frank Rowand <frowand.list@gmail.com>,
	"Grant Likely" <grant.likely@linaro.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Zefan Li <lizefan@huawei.com>, Xinwei Hu <huxinwei@huawei.com>,
	Tianhong Ding <dingtianhong@huawei.com>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH 2/3] of/numa: fix a memory@ dt node can only contains one memory block
Date: Fri, 27 May 2016 15:04:11 +0800	[thread overview]
Message-ID: <5747F16B.5050404@huawei.com> (raw)
In-Reply-To: <CAL_JsqJXu36qYMOZeWDnMQ8BnOxMrixv5N70hvTjDixhMCQKRw@mail.gmail.com>



On 2016/5/27 12:20, Rob Herring wrote:
> On Thu, May 26, 2016 at 10:36 PM, Leizhen (ThunderTown)
> <thunder.leizhen@huawei.com> wrote:
>>
>>
>> On 2016/5/26 21:13, Rob Herring wrote:
>>> On Thu, May 26, 2016 at 10:43:58AM +0800, Zhen Lei wrote:
>>>> For a normal memory@ devicetree node, its reg property can contains more
>>>> memory blocks.
>>>>
>>>> Because we don't known how many memory blocks maybe contained, so we try
>>>> from index=0, increase 1 until error returned(the end).
>>>>
>>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>>> ---
>>>>  drivers/of/of_numa.c | 30 ++++++++++++++++++++----------
>>>>  1 file changed, 20 insertions(+), 10 deletions(-)
>>>>
>>>> diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
>>>> index 21d831f..2c5f249 100644
>>>> --- a/drivers/of/of_numa.c
>>>> +++ b/drivers/of/of_numa.c
>>>> @@ -63,7 +63,7 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>      struct device_node *np = NULL;
>>>>      struct resource rsrc;
>>>>      u32 nid;
>>>> -    int r = 0;
>>>> +    int i, r = 0;
>>>>
>>>>      for (;;) {
>>>>              np = of_find_node_by_type(np, "memory");
>>>> @@ -82,17 +82,27 @@ static int __init of_numa_parse_memory_nodes(void)
>>>>                      /* some other error */
>>>>                      break;
>>>>
>>>> -            r = of_address_to_resource(np, 0, &rsrc);
>>>> -            if (r) {
>>>> -                    pr_err("NUMA: bad reg property in memory node\n");
>>>> -                    break;
>>>> +            for (i = 0; ; i++) {
>>>> +                    r = of_address_to_resource(np, i, &rsrc);
>>>> +                    if (r) {
>>>> +                            /* reached the end of of_address */
>>>> +                            if (i > 0) {
>>>> +                                    r = 0;
>>>> +                                    break;
>>>> +                            }
>>>> +
>>>> +                            pr_err("NUMA: bad reg property in memory node\n");
>>>> +                            goto finished;
>>>> +                    }
>>>> +
>>>> +                    r = numa_add_memblk(nid, rsrc.start,
>>>> +                                        rsrc.end - rsrc.start + 1);
>>>> +                    if (r)
>>>> +                            goto finished;
>>>>              }
>>>> -
>>>> -            r = numa_add_memblk(nid, rsrc.start,
>>>> -                                rsrc.end - rsrc.start + 1);
>>>> -            if (r)
>>>> -                    break;
>>>>      }
>>>> +
>>>> +finished:
>>>>      of_node_put(np);
>>>
>>> This function can be simplified down to:
>>>
>>>       for_each_node_by_type(np, "memory") {
>> OK, That's good.
>>
>>>               r = of_property_read_u32(np, "numa-node-id", &nid);
>>>               if (r == -EINVAL)
>>>                       /*
>>>                        * property doesn't exist if -EINVAL, continue
>>>                        * looking for more memory nodes with
>>>                        * "numa-node-id" property
>>>                        */
>>>                       continue;
>> Hi, everybody:
>>     If some "memory" node contains "numa-node-id", but some others missed. Can we simply ignored it?
>> I think we should break out too, and faking to only have node0.
> 
> Continuing to work is probably better than not.
> 
>>
>>>               else if (r)
>>>                       /* some other error */
>>>                       break;
>>>
>>>               r = of_address_to_resource(np, 0, &rsrc);
>>>               for (i = 0; !r; i++, r = of_address_to_resource(np, i,
>>
>> But r(non-zero) is just break this loop, the original is break the outer for (;;) loop
> 
> It is not really the kernel's job to validate the DT. If there's
> random things in it then kernel's behavior is undefined.
> 
>>
>> How about as below?
>>
>>         for_each_node_by_type(np, "memory") {
>>                 ... ...
>>
>>                 for (i = 0; !of_address_to_resource(np, i, &rsrc); i++) {
>>                         r = numa_add_memblk(nid, rsrc.start,
>>                                             rsrc.end - rsrc.start + 1);
>>                         if (r)
>>                                 goto finished;
>>                 }
>>
>>                 if (!i)
>>                         pr_err("NUMA: bad reg property in memory node\n");
>>         }
>>
>> finished:
> 
> Please try to avoid the goto. You can check r in the outer loop too.

OK. I have rewritten this function according to your advice.

	for_each_node_by_type(np, "memory") {
                r = of_property_read_u32(np, "numa-node-id", &nid);
                if (r == -EINVAL)
                        /*
                         * property doesn't exist if -EINVAL, continue
                         * looking for more memory nodes with
                         * "numa-node-id" property
                         */
                        continue;
									//I deleted the break of "some other error", and it will break in below "if (!i || r)" branch

                for (i = 0; !r && !of_address_to_resource(np, i, &rsrc); i++)
                        r = numa_add_memblk(nid, rsrc.start,
                                            rsrc.end - rsrc.start + 1);

                if (!i || r) {
                        of_node_put(np);				//I moved here, so that it looks more clear. Because in the normal use of for_each_node_by_type, of_node_put is not required
                        pr_err("NUMA: bad property in memory node\n");	//Deleted "reg", so that it's suitable or harmless for other error cases
                        break;
                }
        }

	return r;

> 
> Rob
> 
> .
> 

  reply	other threads:[~2016-05-27  7:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  2:43 [PATCH 1/3] of/numa: remove a duplicated pr_debug information Zhen Lei
2016-05-26  2:43 ` Zhen Lei
2016-05-26  2:43 ` Zhen Lei
2016-05-26  2:43 ` [PATCH 2/3] of/numa: fix a memory@ dt node can only contains one memory block Zhen Lei
2016-05-26  2:43   ` Zhen Lei
2016-05-26  2:43   ` Zhen Lei
2016-05-26 13:13   ` Rob Herring
2016-05-26 13:13     ` Rob Herring
2016-05-27  3:36     ` Leizhen (ThunderTown)
2016-05-27  3:36       ` Leizhen (ThunderTown)
2016-05-27  3:36       ` Leizhen (ThunderTown)
2016-05-27  4:20       ` Rob Herring
2016-05-27  4:20         ` Rob Herring
2016-05-27  4:20         ` Rob Herring
2016-05-27  7:04         ` Leizhen (ThunderTown) [this message]
2016-05-27  7:04           ` Leizhen (ThunderTown)
2016-05-27  7:04           ` Leizhen (ThunderTown)
2016-05-27 16:07       ` David Daney
2016-05-27 16:07         ` David Daney
2016-05-27 16:07         ` David Daney
2016-05-26  2:43 ` [PATCH 3/3] arm64/numa: fix type info Zhen Lei
2016-05-26  2:43   ` Zhen Lei
2016-05-26  2:43   ` Zhen Lei
2016-05-26 16:22   ` Ganapatrao Kulkarni
2016-05-26 16:22     ` Ganapatrao Kulkarni
2016-05-26 16:35     ` Joe Perches
2016-05-26 16:35       ` Joe Perches
2016-05-26 17:12       ` David Daney
2016-05-26 17:12         ` David Daney
2016-05-27  2:35         ` Leizhen (ThunderTown)
2016-05-27  2:35           ` Leizhen (ThunderTown)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5747F16B.5050404@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.