From: Kevin Cernekee <cernekee@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Jan Beulich <JBeulich@novell.com>
Subject: [PATCH V2 1/2] module: Add comments describing how the "strmap" logic works
Date: Sat, 12 Nov 2011 19:08:55 -0800 [thread overview]
Message-ID: <73defb5e4bca04a6431392cc341112b1@localhost> (raw)
Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
---
kernel/module.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 178333c..cf9f1b6 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -2193,6 +2193,13 @@ static void layout_symtab(struct module *mod, struct load_info *info)
src = (void *)info->hdr + symsect->sh_offset;
nsrc = symsect->sh_size / sizeof(*src);
+
+ /*
+ * info->strmap has a '1' bit for each byte of .strtab we want to
+ * keep resident in mod->core_strtab. Everything else in .strtab
+ * is unreferenced by the symbols in mod->core_symtab, and will be
+ * discarded when add_kallsyms() compacts the string table.
+ */
for (ndst = i = 1; i < nsrc; ++i, ++src)
if (is_core_symbol(src, info->sechdrs, info->hdr->e_shnum)) {
unsigned int j = src->st_name;
@@ -2215,6 +2222,8 @@ static void layout_symtab(struct module *mod, struct load_info *info)
/* Append room for core symbols' strings at end of core part. */
info->stroffs = mod->core_size;
+
+ /* First strtab byte (and first symtab entry) are zeroes. */
__set_bit(0, info->strmap);
mod->core_size += bitmap_weight(info->strmap, strsect->sh_size);
}
--
1.7.6.3
next reply other threads:[~2011-11-13 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 3:08 Kevin Cernekee [this message]
2011-11-13 3:08 ` [PATCH V2 2/2] module: Fix performance regression on modules with large symbol tables Kevin Cernekee
2011-11-14 0:35 ` Rusty Russell
2011-11-14 8:48 ` Jan Beulich
2011-11-16 0:24 ` Rusty Russell
2011-11-18 3:15 ` Kevin Cernekee
2011-11-21 5:06 ` Rusty Russell
2011-11-21 6:29 ` Kevin Cernekee
2011-11-21 23:57 ` Rusty Russell
2011-11-21 8:08 ` Jan Beulich
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=73defb5e4bca04a6431392cc341112b1@localhost \
--to=cernekee@gmail.com \
--cc=JBeulich@novell.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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