From: Masahiro Yamada <masahiroy@kernel.org>
To: Hui Su <suhui_kernel@163.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts: update the comments of kallsyms support
Date: Tue, 12 Oct 2021 11:51:30 +0900 [thread overview]
Message-ID: <CAK7LNARhAXKhRbm6UAJ9q=C17XXAUc5M1CPDS=a7-3-X0B1FzQ@mail.gmail.com> (raw)
In-Reply-To: <20211008112438.GA1243425@localhost.localdomain>
On Fri, Oct 8, 2021 at 8:25 PM Hui Su <suhui_kernel@163.com> wrote:
>
> update the comments of kallsyms support
>
> Signed-off-by: Hui Su <suhui_kernel@163.com>
> ---
I added
Fixes: af73d78bd384 ("kbuild: Remove debug info from kallsyms linking")
Applied to linux-kbuild. Thanks.
> scripts/link-vmlinux.sh | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
> index d74cee5c4326..a98c4f045302 100755
> --- a/scripts/link-vmlinux.sh
> +++ b/scripts/link-vmlinux.sh
> @@ -369,14 +369,14 @@ if [ -n "${CONFIG_KALLSYMS}" ]; then
> # kallsyms support
> # Generate section listing all symbols and add it into vmlinux
> # It's a three step process:
> - # 1) Link .tmp_vmlinux1 so it has all symbols and sections,
> + # 1) Link .tmp_vmlinux.kallsyms1 so it has all symbols and sections,
> # but __kallsyms is empty.
> # Running kallsyms on that gives us .tmp_kallsyms1.o with
> # the right size
> - # 2) Link .tmp_vmlinux2 so it now has a __kallsyms section of
> + # 2) Link .tmp_vmlinux.kallsyms2 so it now has a __kallsyms section of
> # the right size, but due to the added section, some
> # addresses have shifted.
> - # From here, we generate a correct .tmp_kallsyms2.o
> + # From here, we generate a correct .tmp_vmlinux.kallsyms2.o
> # 3) That link may have expanded the kernel image enough that
> # more linker branch stubs / trampolines had to be added, which
> # introduces new names, which further expands kallsyms. Do another
> --
> 2.25.1
>
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2021-10-12 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 11:24 [PATCH] scripts: update the comments of kallsyms support Hui Su
2021-10-12 2:51 ` Masahiro Yamada [this message]
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='CAK7LNARhAXKhRbm6UAJ9q=C17XXAUc5M1CPDS=a7-3-X0B1FzQ@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=suhui_kernel@163.com \
/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).