From: Naveen N Rao <naveen@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: linuxppc-dev@lists.ozlabs.org, bpf@vger.kernel.org,
Jiri Olsa <olsajiri@gmail.com>,
dwarves@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: ppc64le vmlinuz is huge when building with BTF
Date: Fri, 16 Jun 2023 16:28:53 +0530 [thread overview]
Message-ID: <1686912543.c6zqyw5s4x.naveen@kernel.org> (raw)
In-Reply-To: <ZIt11crcIjfyeygA@codewreck.org>
[Cc linuxppc-dev]
Dominique Martinet wrote:
>
> Alan Maguire wrote on Thu, Jun 15, 2023 at 03:31:49PM +0100:
>> However the problem I suspect is this:
>>
>> 51 .debug_info 0a488b55 0000000000000000 0000000000000000 026f8d20
>> 2**0
>> CONTENTS, READONLY, DEBUGGING
>> [...]
>>
>> The debug info hasn't been stripped, so I suspect the packaging spec
>> file or equivalent - in perhaps trying to preserve the .BTF section -
>> is preserving debug info too. DWARF needs to be there at BTF
>> generation time in vmlinux but is usually stripped for non-debug
>> packages.
>
> Thanks Alan and Eduard!
> I guess I should have checked that first, it helps.
>
> We're not stripping anything in vmlinuz for other archs -- the linker
> script already should be including only the bare minimum to decompress
> itself (+compressed useful bits), so I guess it's a Kbuild issue for the
> arch.
For a related discussion, see:
http://lore.kernel.org/CAK18DXZKs2PNmLndeGYqkPxmrrBR=6ca3bhyYCj=GhyA7dHfAQ@mail.gmail.com
> We can add a strip but I unfortunately have no way of testing ppc build,
> I'll ask around the build linux-kbuild and linuxppc-dev lists if that's
> expected; it shouldn't be that bad now that's figured out.
Stripping vmlinux would indeed be the way to go. As mentioned in the
above link, fedora also packages a strip'ed vmlinux for ppc64le:
https://src.fedoraproject.org/rpms/kernel/blob/4af17bffde7a1eca9ab164e5de0e391c277998a4/f/kernel.spec#_1797
- Naveen
next parent reply other threads:[~2023-06-16 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZIqGSJDaZObKjLnN@codewreck.org>
[not found] ` <ZIrONqGJeATpbg3Y@krava>
[not found] ` <ZIr7aaVpOaP8HjbZ@codewreck.org>
[not found] ` <6b26dfef-016c-43df-07f5-c2f88157d1dc@oracle.com>
[not found] ` <ZIt11crcIjfyeygA@codewreck.org>
2023-06-16 10:58 ` Naveen N Rao [this message]
2023-06-16 12:00 ` ppc64le vmlinuz is huge when building with BTF Dominique Martinet
2023-06-16 17:12 ` Naveen N Rao
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=1686912543.c6zqyw5s4x.naveen@kernel.org \
--to=naveen@kernel.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=asmadeus@codewreck.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olsajiri@gmail.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).