From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Tom Rini <trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Cc: Devicetree Compiler
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Subject: Re: [PATCH] libfdt: Make fdt{32,64}_ld() default to assuming unaligned access is safe
Date: Wed, 4 Nov 2020 11:29:28 -0600 [thread overview]
Message-ID: <CAL_JsqL30DTr4reQ0r98Z7vO6CNaKZPFNWMYzDVN+QPzUq3APw@mail.gmail.com> (raw)
In-Reply-To: <20201104134645.30138-1-trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
On Wed, Nov 4, 2020 at 7:46 AM Tom Rini <trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org> wrote:
>
> Commits 6dcb8ba4 "libfdt: Add helpers for accessing unaligned words"
> introduced changes to support unaligned reads for ARM platforms and
> 11738cf01f15 "libfdt: Don't use memcpy to handle unaligned reads on ARM"
> improved the performance of these helpers.
>
> On further discussion, while there are potential cases where we could be
> used on platforms that do not fixup unaligned reads for us, making this
> choice the default is very expensive in terms of binary size and access
> time. To address this, suffix the existing fdt{32,64}_ld functions with
> _unaligned and introduce new load functions that call
> fdt{32,64}_to_cpu() as was done prior to the above mentioned commits.
>
> Signed-off-by: Tom Rini <trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
> ---
> libfdt/libfdt.h | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
> index b600c8d6dd41..307ba745c92f 100644
> --- a/libfdt/libfdt.h
> +++ b/libfdt/libfdt.h
> @@ -126,13 +126,22 @@ static inline void *fdt_offset_ptr_w(void *fdt, int offset, int checklen)
> uint32_t fdt_next_tag(const void *fdt, int offset, int *nextoffset);
>
> /*
> - * Alignment helpers:
> - * These helpers access words from a device tree blob. They're
> - * built to work even with unaligned pointers on platforms (ike
> - * ARM) that don't like unaligned loads and stores
> + * Load functions. Assume that we are on a platform where unaligned memory
> + * reads will be handled in a graceful manner and that we do not need to ensure
> + * our reads are aligned. If this is not the case there are _unaligned
> + * versions of these functions that follow and can be used.
> */
> -
> static inline uint32_t fdt32_ld(const fdt32_t *p)
> +{
> + return fdt32_to_cpu(*p);
This changes the public behavior of fdt32_ld() which is one of the
things David was against.
I think we want a _fdt32_ld or fdt32_ld_internal or ?? which is
internal only and doesn't create another ABI.
Rob
next prev parent reply other threads:[~2020-11-04 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 13:46 [PATCH] libfdt: Make fdt{32,64}_ld() default to assuming unaligned access is safe Tom Rini
[not found] ` <20201104134645.30138-1-trini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2020-11-04 17:29 ` Rob Herring [this message]
[not found] ` <CAL_JsqL30DTr4reQ0r98Z7vO6CNaKZPFNWMYzDVN+QPzUq3APw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-11-04 17:34 ` Tom Rini
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=CAL_JsqL30DTr4reQ0r98Z7vO6CNaKZPFNWMYzDVN+QPzUq3APw@mail.gmail.com \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trini-OWPKS81ov/FWk0Htik3J/w@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 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).