From: Borislav Petkov <bp@alien8.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] kbuild: Disable extra debugging info in .s output
Date: Thu, 31 Jan 2019 12:58:20 +0100 [thread overview]
Message-ID: <20190131115820.GF6749@zn.tnic> (raw)
In-Reply-To: <20190121095338.8565-1-bp@alien8.de>
Ping?
On Mon, Jan 21, 2019 at 10:53:38AM +0100, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> Modern gcc adds view assignments, reset assertion checking in .loc
> directives and a couple more additional debug markers, which clutters
> the asm output unnecessarily:
>
> For example:
>
> bsp_resume:
> .LFB3466:
> .loc 1 1868 1 is_stmt 1 view -0
> .cfi_startproc
> .loc 1 1869 2 view .LVU73
> # arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
> .loc 1 1869 14 is_stmt 0 view .LVU74
> movq this_cpu(%rip), %rax # this_cpu, this_cpu
> movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
> # arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
> .loc 1 1869 5 view .LVU75
> testq %rax, %rax # _2
> je .L8 #,
> .loc 1 1870 3 is_stmt 1 view .LVU76
> movq $boot_cpu_data, %rdi #,
> jmp __x86_indirect_thunk_rax
>
> or
> .loc 2 57 9 view .LVU478
> .loc 2 57 9 view .LVU479
> .loc 2 57 9 view .LVU480
> .loc 2 57 9 view .LVU481
> .LBB1385:
> .LBB1383:
> .LBB1379:
> .LBB1377:
> .LBB1375:
> .loc 2 57 9 view .LVU482
> .loc 2 57 9 view .LVU483
> movl %edi, %edx # cpu, cpu
> .LVL87:
> .loc 2 57 9 is_stmt 0 view .LVU484
>
> That MOV in there is drowned in debugging information and latter makes
> it hard to follow the asm. And that DWARF info is not really needed for
> asm output staring.
>
> Disable the debug information generation which clutters the asm output
> unnecessarily:
>
> bsp_resume:
> .LFB3466:
> .loc 1 1868 1
> # arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
> .loc 1 1869 14
> movq this_cpu(%rip), %rax # this_cpu, this_cpu
> movq 64(%rax), %rax # this_cpu.94_1->c_bsp_resume, _2
> # arch/x86/kernel/cpu/common.c:1869: if (this_cpu->c_bsp_resume)
> .loc 1 1869 5
> testq %rax, %rax # _2
> je .L8 #,
> # arch/x86/kernel/cpu/common.c:1870: this_cpu->c_bsp_resume(&boot_cpu_data);
> .loc 1 1870 3
> movq $boot_cpu_data, %rdi #,
> jmp __x86_indirect_thunk_rax
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Michal Marek <michal.lkml@markovi.net>
> Cc: linux-kbuild@vger.kernel.org
> ---
> scripts/Makefile.build | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> index fd03d60f6c5a..4f33fdab89d2 100644
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@ -103,8 +103,12 @@ modkern_cflags = \
> $(KBUILD_CFLAGS_KERNEL) $(CFLAGS_KERNEL))
> quiet_modtag = $(if $(part-of-module),[M], )
>
> +disable_extra_cc_dbg := $(call cc-option,-gno-as-locview-support)
> +disable_extra_cc_dbg += $(call cc-option,-fno-dwarf2-cfi-asm)
> +disable_extra_cc_dbg += $(call cc-option,-feliminate-unused-debug-symbols)
> +disable_extra_cc_dbg += $(call cc-option,-gno-statement-frontiers)
> quiet_cmd_cc_s_c = CC $(quiet_modtag) $@
> -cmd_cc_s_c = $(CC) $(c_flags) $(DISABLE_LTO) -fverbose-asm -S -o $@ $<
> +cmd_cc_s_c = $(CC) $(c_flags) $(DISABLE_LTO) $(disable_extra_cc_dbg) -fverbose-asm -S -o $@ $<
>
> $(obj)/%.s: $(src)/%.c FORCE
> $(call if_changed_dep,cc_s_c)
> --
> 2.19.1
>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-31 11:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 9:53 [PATCH] kbuild: Disable extra debugging info in .s output Borislav Petkov
2019-01-31 11:58 ` Borislav Petkov [this message]
2019-02-01 3:06 ` Masahiro Yamada
2019-02-01 9:42 ` Borislav Petkov
2019-02-01 10:09 ` Masahiro Yamada
2019-02-01 10:23 ` Borislav Petkov
2019-02-01 11:03 ` Masahiro Yamada
2019-02-01 10:30 ` Borislav Petkov
2019-02-01 10:36 ` Borislav Petkov
2019-02-01 11:58 ` Masahiro Yamada
2019-02-01 15:11 ` Borislav Petkov
2019-02-02 13:48 ` Masahiro Yamada
2019-02-02 14:42 ` Borislav Petkov
2019-02-06 10:47 ` Borislav Petkov
2019-02-10 6:51 ` Masahiro Yamada
2019-02-10 12:39 ` Borislav Petkov
2019-02-18 8:30 ` Borislav Petkov
2019-02-18 9:10 ` Masahiro Yamada
2019-02-18 14:31 ` Borislav Petkov
2019-02-19 23:55 ` Masahiro Yamada
2019-02-01 10:51 ` Masahiro Yamada
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=20190131115820.GF6749@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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