From: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Grant Likely <glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: Pantelis Antoniou
<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] vsprintf: Add %p extension "%pOF" for device tree
Date: Thu, 22 Jun 2017 20:01:52 -0700 [thread overview]
Message-ID: <1498186912.24295.9.camel@perches.com> (raw)
In-Reply-To: <20170622204445.14930-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Thu, 2017-06-22 at 15:44 -0500, Rob Herring wrote:
> From: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
>
> 90% of the usage of device node's full_name is printing it out in a
> kernel message. However, storing the full path for every node is
> wasteful and redundant. With a custom format specifier, we can generate
> the full path at run-time and eventually remove the full path from every
> node.
>
> For instance typical use is:
> pr_info("Frobbing node %s\n", node->full_name);
>
> Which can be written now as:
> pr_info("Frobbing node %pOF\n", node);
I still think this should use another identifier like
%pO for object then another letter for type of object
maybe N for node.
And F is flags, f is name
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> @@ -1470,6 +1471,131 @@ char *flags_string(char *buf, char *end, void *flags_ptr, const char *fmt)
> return format_flags(buf, end, flags, names);
> }
>
> +static int device_node_calc_depth(const struct device_node *np)
> +{
> + int d;
> +
> + for (d = 0; np; d++)
> + np = np->parent;
> +
> + return d;
> +}
> +
> +static noinline_for_stack
> +char *device_node_gen_full_name(const struct device_node *np, char *buf, char *end)
> +{
> + int i;
> + int depth = device_node_calc_depth(np);
> + static const struct printf_spec strspec = {
> + .field_width = -1,
> + .precision = -1,
> + };
> + const struct device_node *nodes[depth];
> +
> + if (!depth)
> + returnuf;
> + /* special case for root node */
> + if (depth == 1)
> + return string(buf, end, "/", strspec);
> +
> + depth--;
> + for (i = depth - 1; i >= 0; i--) {
> + nodes[i] = np;
> + np = np->parent;
> + }
> + for (i = 0; i < depth; i++) {
> + buf = string(buf, end, "/", strspec);
> + buf = string(buf, end, kbasename(nodes[i]->full_name), strspec);
> + }
> + return buf;
> +}
I think there should be another function to get
a particular struct device_node * at a particular
depth to avoid all the pointers on stack.
Basically, adapt the for (i = depth - 1 loop to
a function that returns nodes[i]
--
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: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>,
Grant Likely <glikely@secretlab.ca>,
Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vsprintf: Add %p extension "%pOF" for device tree
Date: Thu, 22 Jun 2017 20:01:52 -0700 [thread overview]
Message-ID: <1498186912.24295.9.camel@perches.com> (raw)
In-Reply-To: <20170622204445.14930-1-robh@kernel.org>
On Thu, 2017-06-22 at 15:44 -0500, Rob Herring wrote:
> From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
>
> 90% of the usage of device node's full_name is printing it out in a
> kernel message. However, storing the full path for every node is
> wasteful and redundant. With a custom format specifier, we can generate
> the full path at run-time and eventually remove the full path from every
> node.
>
> For instance typical use is:
> pr_info("Frobbing node %s\n", node->full_name);
>
> Which can be written now as:
> pr_info("Frobbing node %pOF\n", node);
I still think this should use another identifier like
%pO for object then another letter for type of object
maybe N for node.
And F is flags, f is name
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> @@ -1470,6 +1471,131 @@ char *flags_string(char *buf, char *end, void *flags_ptr, const char *fmt)
> return format_flags(buf, end, flags, names);
> }
>
> +static int device_node_calc_depth(const struct device_node *np)
> +{
> + int d;
> +
> + for (d = 0; np; d++)
> + np = np->parent;
> +
> + return d;
> +}
> +
> +static noinline_for_stack
> +char *device_node_gen_full_name(const struct device_node *np, char *buf, char *end)
> +{
> + int i;
> + int depth = device_node_calc_depth(np);
> + static const struct printf_spec strspec = {
> + .field_width = -1,
> + .precision = -1,
> + };
> + const struct device_node *nodes[depth];
> +
> + if (!depth)
> + returnuf;
> + /* special case for root node */
> + if (depth == 1)
> + return string(buf, end, "/", strspec);
> +
> + depth--;
> + for (i = depth - 1; i >= 0; i--) {
> + nodes[i] = np;
> + np = np->parent;
> + }
> + for (i = 0; i < depth; i++) {
> + buf = string(buf, end, "/", strspec);
> + buf = string(buf, end, kbasename(nodes[i]->full_name), strspec);
> + }
> + return buf;
> +}
I think there should be another function to get
a particular struct device_node * at a particular
depth to avoid all the pointers on stack.
Basically, adapt the for (i = depth - 1 loop to
a function that returns nodes[i]
next prev parent reply other threads:[~2017-06-23 3:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 20:30 [PATCH 0/4] DT printf format specifiers Rob Herring
2017-06-14 20:30 ` Rob Herring
[not found] ` <20170614203025.7581-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-14 20:30 ` [PATCH 1/4] of: use kbasename instead of open coding Rob Herring
2017-06-14 20:30 ` Rob Herring
[not found] ` <20170614203025.7581-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-17 17:30 ` Andy Shevchenko
2017-06-17 17:30 ` Andy Shevchenko
2017-06-14 20:30 ` [PATCH 2/4] of: find_node_by_full_name rewrite to compare each level Rob Herring
2017-06-14 20:30 ` [PATCH 3/4] of: Custom printk format specifier for device node Rob Herring
[not found] ` <20170614203025.7581-4-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-14 20:56 ` Joe Perches
2017-06-14 20:56 ` Joe Perches
[not found] ` <1497473808.18751.70.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-06-15 12:30 ` Rob Herring
2017-06-15 12:30 ` Rob Herring
[not found] ` <CAL_JsqJ_cc46Hf2XdZoXkgZyOh+0KXVXfeWYe1100E9vuRt12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-15 16:51 ` Joe Perches
2017-06-15 16:51 ` Joe Perches
2017-06-15 21:26 ` Rob Herring
2017-06-15 21:26 ` Rob Herring
2017-06-15 21:50 ` Joe Perches
2017-06-15 21:50 ` Joe Perches
2017-06-22 20:44 ` [PATCH v2] vsprintf: Add %p extension "%pOF" for device tree Rob Herring
2017-06-22 20:44 ` Rob Herring
2017-06-22 22:44 ` Randy Dunlap
[not found] ` <d22444aa-39da-ec74-42a1-63f1fa40c7d3-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-06-23 14:08 ` Rob Herring
2017-06-23 14:08 ` Rob Herring
[not found] ` <20170622204445.14930-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-23 3:01 ` Joe Perches [this message]
2017-06-23 3:01 ` Joe Perches
[not found] ` <1498186912.24295.9.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-06-23 14:13 ` Rob Herring
2017-06-23 14:13 ` Rob Herring
2017-06-23 17:30 ` [PATCH v3] " Rob Herring
[not found] ` <20170623173053.636-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-23 17:38 ` Joe Perches
2017-06-23 17:38 ` Joe Perches
2017-06-14 20:30 ` [PATCH 4/4] of: Convert to using %pOF instead of full_name Rob Herring
[not found] ` <20170614203025.7581-5-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-14 20:58 ` Joe Perches
2017-06-14 20:58 ` Joe Perches
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=1498186912.24295.9.camel@perches.com \
--to=joe-6d6dil74uinbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.