From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Sven Schnelle <svens@stackframe.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Compressed kernels currently won't boot
Date: Wed, 31 Jul 2019 14:01:34 -0700 [thread overview]
Message-ID: <1564606894.3319.72.camel@HansenPartnership.com> (raw)
In-Reply-To: <20190731194413.GB23520@t470p.stackframe.org>
On Wed, 2019-07-31 at 21:44 +0200, Sven Schnelle wrote:
> Hi James,
>
> On Wed, Jul 31, 2019 at 12:40:12PM -0700, James Bottomley wrote:
>
> > What about causing the compressed make to build both a stripped and
> > a non-stripped bzImage (say sbzImage and bzImage). That way you
> > always have the stripped one available for small size things like
> > boot from tape or DVD? but in the usual case we use the bzImage
> > with full contents.
>
> In that case we would also need to build two lifimages - how about
> adding a config option option? Something like "Strip debug
> information from compressed kernel images"?
Actually, I just looked at what x86 does. It has this in the
arch/x86/boot/compressed/Makefile:
OBJCOPYFLAGS_vmlinux.bin := -R .comment -S
$(obj)/vmlinux.bin: vmlinux FORCE
$(call if_changed,objcopy)
So it basically strips all the debug information from the kernel before
compressing, which argues there's no need to retain the information
because x86 doesn't bother.
James
next prev parent reply other threads:[~2019-07-31 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:44 Compressed kernels currently won't boot James Bottomley
2019-07-31 17:30 ` Sven Schnelle
2019-07-31 17:50 ` James Bottomley
2019-07-31 19:40 ` James Bottomley
2019-07-31 19:44 ` Sven Schnelle
2019-07-31 19:46 ` Helge Deller
2019-07-31 19:56 ` James Bottomley
2019-07-31 20:19 ` Helge Deller
2019-07-31 20:49 ` James Bottomley
2019-07-31 21:44 ` Helge Deller
2019-08-01 1:37 ` James Bottomley
2019-07-31 21:01 ` James Bottomley [this message]
2019-07-31 21:08 ` Sven Schnelle
2019-07-31 21:13 ` Helge Deller
2019-07-31 21:51 ` Helge Deller
2019-08-01 8:10 ` Sven Schnelle
2019-07-31 19:57 ` Helge Deller
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=1564606894.3319.72.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-parisc@vger.kernel.org \
--cc=svens@stackframe.org \
/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).