From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Michal Marek <mmarek@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: include core debug info when DEBUG_INFO_REDUCED
Date: Thu, 11 Jun 2015 14:32:48 +0200 [thread overview]
Message-ID: <87eglie87j.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <1426902601-13524-1-git-send-email-linux@rasmusvillemoes.dk> (Rasmus Villemoes's message of "Sat, 21 Mar 2015 02:50:01 +0100")
On Sat, Mar 21 2015, Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
> With CONFIG_DEBUG_INFO_REDUCED, we do get quite a lot of debug info
> (around 22.7 MB for a defconfig+DEBUG_INFO_REDUCED). However, the
> "basenames must match" rule used by -femit-struct-debug-baseonly
> option means that we miss some core data structures, such as struct
> {device, file, inode, mm_struct, page} etc.
>
> We can easily get these included as well, while still getting the
> benefits of CONFIG_DEBUG_INFO_REDUCED (faster build times and smaller
> individual object files): All it takes is a dummy translation unit
> including a few strategic headers and compiled with a flag overriding
> -femit-struct-debug-baseonly.
>
> This increases the size of .debug_info by ~0.3%, but these 90 KB
> contain some rather useful info.
>
Any comments on this patch? I know it's a little hacky, but I do find it
rather useful. For example, I just noticed that pahole shows this
struct audit_names {
struct list_head list; /* 0 0 */
/* XXX 16 bytes hole, try to pack */
when applied to a vmlinux built with DEBUG_INFO_REDUCED, since debug
info for struct list_head is not included. The same is true for a lot of
other types which are often embedded in structs (e.g. spinlock_t and
atomic_t). I could of course just compile without DEBUG_INFO_REDUCED,
but the time and space savings of that are real and sad to lose (my tree
is 1.8 GB larger when I compile without it).
Rasmus
next prev parent reply other threads:[~2015-06-11 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 1:50 [PATCH] kbuild: include core debug info when DEBUG_INFO_REDUCED Rasmus Villemoes
2015-06-11 12:32 ` Rasmus Villemoes [this message]
2015-06-11 13:35 ` Michal Marek
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=87eglie87j.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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