From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C6E1C433FF for ; Wed, 31 Jul 2019 21:08:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 133832067D for ; Wed, 31 Jul 2019 21:08:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=duncanthrax.net header.i=@duncanthrax.net header.b="YFEwC0nh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729190AbfGaVIW (ORCPT ); Wed, 31 Jul 2019 17:08:22 -0400 Received: from smtp.duncanthrax.net ([89.31.1.170]:40765 "EHLO smtp.duncanthrax.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727273AbfGaVIW (ORCPT ); Wed, 31 Jul 2019 17:08:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=duncanthrax.net; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date; bh=0WVLgDtCTKMu0uyzk3QL3EjYuVer6Jad86ge8XH+tSY=; b=YFEwC0nh/i+LNhRAbjRI4nxcbu cOIizoIgteiltoF2D/LAgkH9giWmcUU1srDc8ruRGsV9Q6gwO5XB8YVgPa+avNBL0yi4bUO0He4th 8cd3JWQgFGk+gFsjTSQFeE9270o39BMUYvlM0A2ztRQH9yUpKU70EA4zGYkqWv48UF1A=; Received: from [134.3.44.134] (helo=t470p.stackframe.org) by smtp.eurescom.eu with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1hsvpd-00028Y-BX; Wed, 31 Jul 2019 23:08:21 +0200 Date: Wed, 31 Jul 2019 23:08:19 +0200 From: Sven Schnelle To: James Bottomley Cc: Parisc List , deller@gmx.de Subject: Re: Compressed kernels currently won't boot Message-ID: <20190731210819.GE23520@t470p.stackframe.org> References: <1564591443.3319.30.camel@HansenPartnership.com> <20190731173016.GA23520@t470p.stackframe.org> <1564595402.3319.40.camel@HansenPartnership.com> <1564602012.3319.45.camel@HansenPartnership.com> <20190731194413.GB23520@t470p.stackframe.org> <1564606894.3319.72.camel@HansenPartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1564606894.3319.72.camel@HansenPartnership.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-parisc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org 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"! :-) Regards Sven