From: Nick Alcock <nick.alcock@oracle.com>
To: jeyu@kernel.org, masahiroy@kernel.org
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
arnd@arndb.de, eugene.loh@oracle.com, kris.van.hees@oracle.com
Subject: [PATCH v4 3/7] kbuild: generate an address ranges map at vmlinux link time
Date: Tue, 3 Aug 2021 18:16:04 +0100 [thread overview]
Message-ID: <20210803171608.509163-4-nick.alcock@oracle.com> (raw)
In-Reply-To: <20210803171608.509163-1-nick.alcock@oracle.com>
This emits a new file, .tmp_vmlinux.ranges, which maps address
range/size pairs in vmlinux to the object files which make them up,
e.g., in part:
0x0000000000000000 0x30 arch/x86/kernel/cpu/common.o
0x0000000000001000 0x1000 arch/x86/events/intel/ds.o
0x0000000000002000 0x4000 arch/x86/kernel/irq_64.o
0x0000000000006000 0x5000 arch/x86/kernel/process.o
0x000000000000b000 0x1000 arch/x86/kernel/cpu/common.o
0x000000000000c000 0x5000 arch/x86/mm/cpu_entry_area.o
0x0000000000011000 0x10 arch/x86/kernel/espfix_64.o
0x0000000000011010 0x2 arch/x86/kernel/cpu/common.o
[...]
In my simple tests this seems to work with clang too, but if I'm not
sure how stable the format of clang's linker mapfiles is: if it turns
out not to work in some versions, the mapfile-massaging awk script added
here might need some adjustment.
Signed-off-by: Nick Alcock <nick.alcock@oracle.com>
---
scripts/link-vmlinux.sh | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 0e0f6466b18d..00ad1b4b0055 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -178,6 +178,7 @@ vmlinux_link()
objects="--whole-archive \
vmlinux.o \
--no-whole-archive \
+ -Map=.tmp_vmlinux.map \
${@}"
else
objects="--whole-archive \
@@ -186,6 +187,7 @@ vmlinux_link()
--start-group \
${KBUILD_VMLINUX_LIBS} \
--end-group \
+ -Map=.tmp_vmlinux.map \
${@}"
fi
@@ -201,6 +203,7 @@ vmlinux_link()
-Wl,--start-group \
${KBUILD_VMLINUX_LIBS} \
-Wl,--end-group \
+ -Wl,-Map=.tmp_vmlinux.map \
${@}"
${CC} ${CFLAGS_vmlinux} \
@@ -259,6 +262,19 @@ kallsyms()
{
local kallsymopt;
+ # read the linker map to identify ranges of addresses:
+ # - for each *.o file, report address, size, pathname
+ # - most such lines will have four fields
+ # - but sometimes there is a line break after the first field
+ # - start reading at "Linker script and memory map"
+ # - stop reading at ".brk"
+ ${AWK} '
+ /\.o$/ && start==1 { print $(NF-2), $(NF-1), $NF }
+ /^Linker script and memory map/ { start = 1 }
+ /^\.brk/ { exit(0) }
+ ' .tmp_vmlinux.map | sort > .tmp_vmlinux.ranges
+
+ # get kallsyms options
if [ -n "${CONFIG_KALLSYMS_ALL}" ]; then
kallsymopt="${kallsymopt} --all-symbols"
fi
--
2.32.0.255.gd9b1d14a2a
next prev parent reply other threads:[~2021-08-03 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 17:16 [PATCH v4] kallsyms: new /proc/kallmodsyms with builtin modules Nick Alcock
2021-08-03 17:16 ` [PATCH v4 1/7] kbuild: bring back tristate.conf Nick Alcock
2021-08-03 17:16 ` [PATCH v4 2/7] kbuild: add modules_thick.builtin Nick Alcock
2021-08-03 17:16 ` Nick Alcock [this message]
2021-08-03 17:16 ` [PATCH v4 4/7] kallsyms: introduce sections needed to map symbols to built-in modules Nick Alcock
2021-08-03 22:05 ` kernel test robot
2021-08-03 17:16 ` [PATCH v4 5/7] kallsyms: optimize .kallsyms_modules* Nick Alcock
2021-08-03 17:16 ` [PATCH v4 6/7] kallsyms: add /proc/kallmodsyms Nick Alcock
2021-08-03 17:16 ` [PATCH v4 7/7] kallsyms: add reliable symbol size info Nick Alcock
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=20210803171608.509163-4-nick.alcock@oracle.com \
--to=nick.alcock@oracle.com \
--cc=arnd@arndb.de \
--cc=eugene.loh@oracle.com \
--cc=jeyu@kernel.org \
--cc=kris.van.hees@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@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).