From: Greg KH <gregkh@linuxfoundation.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: stable@vger.kernel.org, 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>
Subject: Re: [PATCH v4.14] x86/purgatory: Don't generate debug info for purgatory.ro
Date: Sun, 23 Apr 2023 15:10:37 +0200 [thread overview]
Message-ID: <2023042328-prelaw-elastic-7d96@gregkh> (raw)
In-Reply-To: <20230421224048.1236703-1-hi@alyssa.is>
On Fri, Apr 21, 2023 at 10:40:48PM +0000, Alyssa Ross wrote:
> 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(+)
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-04-23 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:40 [PATCH v4.14] x86/purgatory: Don't generate debug info for purgatory.ro Alyssa Ross
2023-04-23 13:10 ` Greg KH [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=2023042328-prelaw-elastic-7d96@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dyoung@redhat.com \
--cc=hi@alyssa.is \
--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