From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: mmarek@suse.cz, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 5/6] kbuild: Use single pass kallsyms
Date: Sat, 8 Feb 2014 10:19:20 +0100 [thread overview]
Message-ID: <20140208091920.GA400@x4> (raw)
In-Reply-To: <1391845840-28514-5-git-send-email-ak@linux.intel.com>
On 2014.02.08 at 08:50 +0100, Andi Kleen wrote:
> -vmlinux_link "${kallsymso}" vmlinux
> +vmlinux_link "${kallsymsso}" vmlinux
> +if [ -n "${CONFIG_KALLSYMS}" ] ; then
> + # Now regenerate the kallsyms table and patch it into the
> + # previously linked file. We tell kallsyms to pad it
> + # to the previous length, so that no symbol changes.
> + info KALLSYMS2 .tmp_kallsyms2.o
> + kallsyms vmlinux .tmp_kallsyms2.o $(<.kallsyms_pad)
> +
> + info OBJCOPY .tmp_kallsyms2.bin
> + ${OBJCOPY} -O binary .tmp_kallsyms2.o .tmp_kallsyms2.bin
> +
> + info PATCHFILE vmlinux
> + OFF=$(${OBJDUMP} --section-headers vmlinux |
> + gawk -f ./source/scripts/elf_file_offset \
> + -v section=.kallsyms -v filesize=$(stat -c%s .tmp_kallsyms2.bin) )
> + if [ -z "$OFF" ] ; then
> + echo "Cannot find .kallsyms section in vmlinux binary"
> + exit 1
> + fi
> + scripts/patchfile vmlinux $OFF .tmp_kallsyms2.bin
> +fi
This causes:
gawk: fatal: can't open source file `./source/scripts/elf_file_offset' for reading (No such file or directory)
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 4c5435f420a6..06469556c580 100644
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -213,7 +213,7 @@ if [ -n "${CONFIG_KALLSYMS}" ] ; then
info PATCHFILE vmlinux
OFF=$(${OBJDUMP} --section-headers vmlinux |
- gawk -f ./source/scripts/elf_file_offset \
+ gawk -f ./scripts/elf_file_offset \
-v section=.kallsyms -v filesize=$(stat -c%s .tmp_kallsyms2.bin) )
if [ -z "$OFF" ] ; then
echo "Cannot find .kallsyms section in vmlinux binary"
--
Markus
next prev parent reply other threads:[~2014-02-08 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 7:50 [PATCH 1/6] kbuild: Remove relocations from kallsyms table Andi Kleen
2014-02-08 7:50 ` [PATCH 2/6] kbuild: Put kallsyms into own section Andi Kleen
2014-02-08 7:50 ` [PATCH 3/6] kbuild: Don't include const variable in kallsyms with !KALLSYMS_ALL Andi Kleen
2014-02-08 7:50 ` [PATCH 4/6] kbuild: Support padding in kallsyms tables Andi Kleen
2014-02-08 12:12 ` Markus Trippelsdorf
2014-02-08 17:46 ` Andi Kleen
2014-02-08 18:01 ` Markus Trippelsdorf
2014-02-08 7:50 ` [PATCH 5/6] kbuild: Use single pass kallsyms Andi Kleen
2014-02-08 9:19 ` Markus Trippelsdorf [this message]
2014-02-08 16:01 ` Andi Kleen
2014-02-08 18:00 ` Markus Trippelsdorf
2014-02-08 7:50 ` [PATCH 6/6] kbuild: Remove .dot postfixes in kallsyms Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2014-02-14 21:17 Updated single-pass kallsyms patchkit for LTO Andi Kleen
2014-02-14 21:17 ` [PATCH 5/6] kbuild: Use single pass kallsyms Andi Kleen
2014-02-18 14:24 Single pass kallsyms v3 Andi Kleen
2014-02-18 14:24 ` [PATCH 5/6] kbuild: Use single pass kallsyms Andi Kleen
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=20140208091920.GA400@x4 \
--to=markus@trippelsdorf.de \
--cc=ak@linux.intel.com \
--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