From: Alyssa Ross <hi@alyssa.is>
To: stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Cc: Nick Cao <nickcao@nichi.co>, Ingo Molnar <mingo@kernel.org>,
Pingfan Liu <kernelfans@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Steve Wahl <steve.wahl@hpe.com>, Dave Young <dyoung@redhat.com>,
Alyssa Ross <hi@alyssa.is>
Subject: [PATCH v4.14] x86/purgatory: Don't generate debug info for purgatory.ro
Date: Fri, 21 Apr 2023 22:40:48 +0000 [thread overview]
Message-ID: <20230421224048.1236703-1-hi@alyssa.is> (raw)
From: Pingfan Liu <kernelfans@gmail.com>
Purgatory.ro is a standalone binary that is not linked against the rest of
the kernel. Its image is copied into an array that is linked to the
kernel, and from there kexec relocates it wherever it desires.
Unlike the debug info for vmlinux, which can be used for analyzing crash
such info is useless in purgatory.ro. And discarding them can save about
200K space.
Original:
259080 kexec-purgatory.o
Stripped debug info:
29152 kexec-purgatory.o
Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Reviewed-by: Steve Wahl <steve.wahl@hpe.com>
Acked-by: Dave Young <dyoung@redhat.com>
Link: https://lore.kernel.org/r/1596433788-3784-1-git-send-email-kernelfans@gmail.com
(cherry picked from commit 52416ffcf823ee11aa19792715664ab94757f111)
Signed-off-by: Alyssa Ross <hi@alyssa.is>
---
arch/x86/purgatory/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/purgatory/Makefile b/arch/x86/purgatory/Makefile
index 2f15a2ac4209..2040ddb824c2 100644
--- a/arch/x86/purgatory/Makefile
+++ b/arch/x86/purgatory/Makefile
@@ -20,6 +20,9 @@ KBUILD_CFLAGS := -fno-strict-aliasing -Wall -Wstrict-prototypes -fno-zero-initia
KBUILD_CFLAGS += -m$(BITS)
KBUILD_CFLAGS += $(call cc-option,-fno-PIE)
+AFLAGS_REMOVE_setup-x86_$(BITS).o += -Wa,-gdwarf-2
+AFLAGS_REMOVE_entry64.o += -Wa,-gdwarf-2
+
$(obj)/purgatory.ro: $(PURGATORY_OBJS) FORCE
$(call if_changed,ld)
--
2.37.1
next reply other threads:[~2023-04-21 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:40 Alyssa Ross [this message]
2023-04-23 13:10 ` [PATCH v4.14] x86/purgatory: Don't generate debug info for purgatory.ro Greg KH
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=20230421224048.1236703-1-hi@alyssa.is \
--to=hi@alyssa.is \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelfans@gmail.com \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nickcao@nichi.co \
--cc=stable@vger.kernel.org \
--cc=steve.wahl@hpe.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