From: Joe Perches <joe@perches.com>
To: Elliot Berman <eberman@codeaurora.org>, Jason Baron <jbaron@akamai.com>
Cc: Trilok Soni <tsoni@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "dynamic_debug: Remove unnecessary __used"
Date: Mon, 11 May 2020 11:54:12 -0700 [thread overview]
Message-ID: <59b3e2aac1388209d168a31294dfd2b1f7d21513.camel@perches.com> (raw)
In-Reply-To: <1589221618-21808-1-git-send-email-eberman@codeaurora.org>
On Mon, 2020-05-11 at 11:26 -0700, Elliot Berman wrote:
> This reverts commit c0d2af637863940b1a4fb208224ca7acb905c39f.
>
> Some compilers[1] may break dynamic_hex_dump by optimizing the
> DYNAMIC_DEBUG_BRANCH check inside __dynamic_func_call_no_desc and completely
> removing the dynamic debug metadata. Thus, there is no dynamic_debug control
> site to enable or disable. The if condition is optimized away based on the
> initial value of flags (i.e. if DEBUG macro is present).
>
> [1]: This behavior is present on [aarch64-gnu-linux-gcc (Ubuntu/Linaro
> 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609] and [Android Common Kernel
> toolchain: "Android (6051079 based on r370808) clang version
> 10.0.1"] using arm64 default defconfig + DYNAMIC_DEBUG enabled.
>
> Change-Id: I28e9b86088eee5d5ed2384fbcea2ac2e7337a559
> Signed-off-by: Elliot Berman <eberman@codeaurora.org>
> ---
Change-Id: probably isn't necessary.
Is there a separate mechanism possible to avoid bloating the
otherwise unused content?
> include/linux/dynamic_debug.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/dynamic_debug.h b/include/linux/dynamic_debug.h
> index abcd5fd..7518db4f 100644
> --- a/include/linux/dynamic_debug.h
> +++ b/include/linux/dynamic_debug.h
> @@ -79,7 +79,7 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,
> const char *fmt, ...);
>
> #define DEFINE_DYNAMIC_DEBUG_METADATA(name, fmt) \
> - static struct _ddebug __aligned(8) \
> + static struct _ddebug __used __aligned(8) \
> __attribute__((section("__verbose"))) name = { \
> .modname = KBUILD_MODNAME, \
> .function = __func__, \
next prev parent reply other threads:[~2020-05-11 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 18:26 Elliot Berman
2020-05-11 18:54 ` Joe Perches [this message]
2020-05-11 19:31 ` Elliot Berman
2020-05-11 19:56 ` 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=59b3e2aac1388209d168a31294dfd2b1f7d21513.camel@perches.com \
--to=joe@perches.com \
--cc=eberman@codeaurora.org \
--cc=jbaron@akamai.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsoni@codeaurora.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®