From: Mark Rutland <mark.rutland@arm.com>
To: Marco Elver <elver@google.com>
Cc: will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
arnd@arndb.de, dvyukov@google.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, kasan-dev@googlegroups.com,
paulmck@kernel.org, Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 1/2] asm-generic/atomic: Prefer __always_inline for wrappers
Date: Mon, 25 Nov 2019 17:37:57 +0000 [thread overview]
Message-ID: <20191125173756.GF32635@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20191122154221.247680-1-elver@google.com>
On Fri, Nov 22, 2019 at 04:42:20PM +0100, Marco Elver wrote:
> Prefer __always_inline for atomic wrappers. When building for size
> (CC_OPTIMIZE_FOR_SIZE), some compilers appear to be less inclined to
> inline even relatively small static inline functions that are assumed to
> be inlinable such as atomic ops. This can cause problems, for example in
> UACCESS regions.
From looking at the link below, the problem is tat objtool isn't happy
about non-whiteliested calls within UACCESS regions.
Is that a problem here? are the kasan/kcsan calls whitelisted?
> By using __always_inline, we let the real implementation and not the
> wrapper determine the final inlining preference.
That sounds reasonable to me, assuming that doesn't end up significantly
bloating the kernel text. What impact does this have on code size?
> This came up when addressing UACCESS warnings with CC_OPTIMIZE_FOR_SIZE
> in the KCSAN runtime:
> http://lkml.kernel.org/r/58708908-84a0-0a81-a836-ad97e33dbb62@infradead.org
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Marco Elver <elver@google.com>
> ---
> include/asm-generic/atomic-instrumented.h | 334 +++++++++++-----------
> include/asm-generic/atomic-long.h | 330 ++++++++++-----------
> scripts/atomic/gen-atomic-instrumented.sh | 6 +-
> scripts/atomic/gen-atomic-long.sh | 2 +-
> 4 files changed, 336 insertions(+), 336 deletions(-)
Do we need to do similar for gen-atomic-fallback.sh and the fallbacks
defined in scripts/atomic/fallbacks/ ?
[...]
> diff --git a/scripts/atomic/gen-atomic-instrumented.sh b/scripts/atomic/gen-atomic-instrumented.sh
> index 8b8b2a6f8d68..68532d4f36ca 100755
> --- a/scripts/atomic/gen-atomic-instrumented.sh
> +++ b/scripts/atomic/gen-atomic-instrumented.sh
> @@ -84,7 +84,7 @@ gen_proto_order_variant()
> [ ! -z "${guard}" ] && printf "#if ${guard}\n"
>
> cat <<EOF
> -static inline ${ret}
> +static __always_inline ${ret}
We should add an include of <linux/compiler.h> to the preamble if we're
explicitly using __always_inline.
> diff --git a/scripts/atomic/gen-atomic-long.sh b/scripts/atomic/gen-atomic-long.sh
> index c240a7231b2e..4036d2dd22e9 100755
> --- a/scripts/atomic/gen-atomic-long.sh
> +++ b/scripts/atomic/gen-atomic-long.sh
> @@ -46,7 +46,7 @@ gen_proto_order_variant()
> local retstmt="$(gen_ret_stmt "${meta}")"
>
> cat <<EOF
> -static inline ${ret}
> +static __always_inline ${ret}
Likewise here
Thanks,
Mark.
next prev parent reply other threads:[~2019-11-25 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 15:42 Marco Elver
2019-11-22 15:42 ` [PATCH 2/2] kcsan: Prefer __always_inline for fast-path Marco Elver
2019-11-25 17:37 ` Mark Rutland [this message]
2019-11-25 18:22 ` [PATCH 1/2] asm-generic/atomic: Prefer __always_inline for wrappers Marco Elver
2019-11-25 18:39 ` Mark Rutland
2019-11-26 11:46 ` Marco Elver
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=20191125173756.GF32635@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=will@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
all inboxes | Powered by JetHome®