Re: Compressed kernels currently won't boot

From: Helge Deller <deller@gmx.de>
To: Sven Schnelle <svens@stackframe.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Compressed kernels currently won't boot
Date: Wed, 31 Jul 2019 23:13:38 +0200	[thread overview]
Message-ID: <4a79ab9c-c791-0c61-0664-60eab3567125@gmx.de> (raw)
In-Reply-To: <20190731210819.GE23520@t470p.stackframe.org>

On 31.07.19 23:08, Sven Schnelle wrote:
> Hi,
>
> On Wed, Jul 31, 2019 at 02:01:34PM -0700, James Bottomley wrote:
>> 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.
>
> Nice. So we could convince Helge by saying "Look, x86 is also stripping it"! :-)

I'm fine with doing exactly why x86 does :-)

Helge