From: Frank Rowand <frowand.list@gmail.com>
To: Chintan Pandya <cpandya@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: cache phandle nodes to decrease cost of of_find_node_by_phandle()
Date: Thu, 1 Feb 2018 00:59:02 -0800 [thread overview]
Message-ID: <38cdcae5-ec0f-d1be-b024-1990d4387731@gmail.com> (raw)
In-Reply-To: <5b84a166-c71b-3a41-9e7f-a7624a8441f6@codeaurora.org>
On 01/31/18 22:45, Chintan Pandya wrote:
>
>
> On 2/1/2018 1:35 AM, frowand.list@gmail.com wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>
>> +
>> +static void of_populate_phandle_cache(void)
>> +{
>> + unsigned long flags;
>> + phandle max_phandle;
>> + u32 nodes = 0;
>> + struct device_node *np;
>> +
>> + if (phandle_cache)
>> + return;
>> +
>> + max_phandle = live_tree_max_phandle();
>> +
>> + raw_spin_lock_irqsave(&devtree_lock, flags);
>> +
>> + for_each_of_allnodes(np)
>> + nodes++;
>> +
>> + /* sanity cap for malformed tree */
>> + if (max_phandle > nodes)
>> + max_phandle = nodes;
> Shouldn't we speak up about this in kernel log ? May be WARN_ON() ?
Probably not. If we care enough about a hand coded phandle property
value we should add a check to checkpatch and/or dtc instead of adding
the warning here.
>> +
>> + phandle_cache = kzalloc((max_phandle + 1) * sizeof(*phandle_cache),
>> + GFP_KERNEL);
> kzalloc (might_sleep) in critical context will break.
Yes, thanks.
I also need to ensure memory ordering in of_free_phandle_cache()
to ensure that max_phandle_cache is zero before the cache memory
is freed.
> Anyways, will fix this locally and share test results.
Thanks, I look forward to the results.
> Thanks,
> Chintan
>
next prev parent reply other threads:[~2018-02-01 8:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 20:05 [PATCH] of: cache phandle nodes to decrease cost of of_find_node_by_phandle() frowand.list
2018-01-31 20:10 ` Frank Rowand
[not found] ` <1517429142-25727-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-31 21:43 ` Frank Rowand
[not found] ` <5dd35d8f-c430-237e-9863-2e73556f92ec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-01 14:24 ` Rob Herring
[not found] ` <CAL_JsqLV_bQ2pQ7hCRDP9_31kmKQjggWFDoCia-KmmO5CR3T5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-01 14:26 ` Rob Herring
2018-02-01 21:09 ` Frank Rowand
2018-02-02 3:45 ` Rob Herring
2018-02-02 22:34 ` Frank Rowand
[not found] ` <4f2b3755-9ef1-4817-7436-9f5aafb38b60-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-02 5:53 ` Chintan Pandya
2018-02-03 3:55 ` Frank Rowand
2018-02-01 6:45 ` Chintan Pandya
2018-02-01 8:59 ` Frank Rowand [this message]
[not found] ` <38cdcae5-ec0f-d1be-b024-1990d4387731-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-01 10:31 ` Chintan Pandya
[not found] ` <9e23d32f-05a0-ce8a-41f8-9a1a3d66be37-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-01 19:10 ` Frank Rowand
[not found] ` <fd9f5f63-b08e-602e-1510-85a65889f550-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-02 5:59 ` Chintan Pandya
[not found] ` <567731e8-8f89-bd6e-c3d4-e36400e69198-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-02 21:26 ` Frank Rowand
2018-02-05 12:23 ` Chintan Pandya
[not found] ` <0a178f4b-75fe-0564-7b0e-596f52fca1dc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-07 12:44 ` Chintan Pandya
[not found] ` <1768c791-7456-c1fe-578b-f6245e79746f-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-07 20:09 ` Frank Rowand
2018-02-01 14:34 ` Rob Herring
2018-02-01 21:13 ` Frank Rowand
-- strict thread matches above, loose matches on Subject: below --
2018-01-31 20:02 frowand.list-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1517428977-25653-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-31 20:07 ` Frank Rowand
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=38cdcae5-ec0f-d1be-b024-1990d4387731@gmail.com \
--to=frowand.list@gmail.com \
--cc=cpandya@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).