From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, linux-kernel@vger.kernel.org
Cc: Jim Cromie <jim.cromie@gmail.com>
Subject: [PATCH 0/7] dyndbg: WIP diet plan
Date: Fri, 7 Aug 2020 14:09:47 -0600 [thread overview]
Message-ID: <20200807200957.1269454-1-jim.cromie@gmail.com> (raw)
dynamic-debug metadata is bloated; the __dyndbg linker section is
effectively an array of struct _ddebugs, and its 1st 3 members are
highly repetetive, with 90%, 84%, 45% repeats. Total reported usage
~150kb for ~2600 callsites on my laptop config.
This patchset is one diet plan. it all holds together nicely until the
"cache" commit, when it blows up starting init (or right after freeing
unused kernel image, which Im hoping to do...).
last commit log has the BUG trace from a LOCKDEP build, which reports
stuff I dont quite undertand, except that it looks bad.
Jim Cromie (7):
dyndbg: give %3u width in pr-format, cosmetic only
dyndbg: motivate a diet plan
dyndbg: select ZPOOL in Kconfig.debug
dyndbg: split struct _ddebug in 2, creating _ddebug_callsite
dyndbg: WIP replace __dyndbg_callsite section with a zs-pool copy.
dyndbg: add locking around zpool-add loop in zpool-init
dyndbg: enable 'cache' of active pr_debug callsites
include/asm-generic/vmlinux.lds.h | 4 +
include/linux/dynamic_debug.h | 36 +++--
lib/Kconfig.debug | 1 +
lib/dynamic_debug.c | 220 +++++++++++++++++++++++++-----
4 files changed, 218 insertions(+), 43 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-07 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 20:09 Jim Cromie [this message]
2020-08-07 20:09 ` [PATCH 1/7] dyndbg: give %3u width in pr-format, cosmetic only Jim Cromie
2020-08-07 20:09 ` [PATCH 2/7] dyndbg: motivate a diet plan Jim Cromie
2020-08-07 20:09 ` [PATCH 3/7] dyndbg: select ZPOOL in Kconfig.debug Jim Cromie
2020-08-09 5:05 ` Randy Dunlap
2020-08-09 15:09 ` jim.cromie
2020-08-07 20:09 ` [PATCH 4/7] dyndbg: split struct _ddebug in 2, creating _ddebug_callsite Jim Cromie
2020-08-07 20:09 ` [PATCH 5/7] dyndbg: WIP replace __dyndbg_callsite section with a zs-pool copy Jim Cromie
2020-08-07 23:50 ` kernel test robot
2020-08-07 20:09 ` [PATCH 6/7] dyndbg: add locking around zpool-add loop in zpool-init Jim Cromie
2020-08-07 20:09 ` [PATCH 6/8] dyndbg: ddebug_zpool_remove Jim Cromie
2020-08-07 20:09 ` [PATCH 7/7] dyndbg: enable 'cache' of active pr_debug callsites Jim Cromie
2020-08-09 4:35 ` [dyndbg] 4397a3e7bf: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2020-08-12 15:11 ` jim.cromie
2020-08-07 20:09 ` [PATCH 8/8] dyndbg: add locking around zpool-add loop in zpool-init Jim Cromie
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=20200807200957.1269454-1-jim.cromie@gmail.com \
--to=jim.cromie@gmail.com \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).