Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754225AbdC1WuY (ORCPT ); Tue, 28 Mar 2017 18:50:24 -0400 Received: from terminus.zytor.com ([65.50.211.136]:40591 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751685AbdC1WuW (ORCPT ); Tue, 28 Mar 2017 18:50:22 -0400 Subject: Re: [PATCH] x86/boot: Support uncompressed kernel To: Chao Peng , Arnd Bergmann , Michal Marek References: <1490273467-97948-1-git-send-email-chao.p.peng@linux.intel.com> <20170323153117.GA6356@tigerII.localdomain> <1490333740.2925.7.camel@linux.intel.com> <20170327075817.bb7wda62fcuvfa4b@linutronix.de> <2e97b35f-bb9e-66e4-736d-66313626354e@suse.com> <1490702482.3011.7.camel@linux.intel.com> Cc: Sebastian Andrzej Siewior , Sergey Senozhatsky , Yinghai Lu , Thomas Gleixner , Ingo Molnar , the arch/x86 maintainers , Kees Cook , Baoquan He , "H.J. Lu" , Paul Bolle , Masahiro Yamada , Borislav Petkov , Andrew Morton , Petr Mladek , "David S. Miller" , "Paul E. McKenney" , Andy Lutomirski , Thomas Garnier , Nicolas Pitre , Tejun Heo , Daniel Mack , Helge Deller , Rik van Riel , Linux Kernel Mailing List , linux-kbuild From: "H. Peter Anvin" Message-ID: <3cbfa24b-8bae-7cc9-dcf5-93f02971e673@zytor.com> Date: Tue, 28 Mar 2017 15:38:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1490702482.3011.7.camel@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 611 Lines: 17 On 03/28/17 05:01, Chao Peng wrote: >> >> I guess the next step would be to use CONFIG_XIP_KERNEL on x86, >> which requires an uncompressed kernel but has the additional advantage >> of sharing the read-only sections of the kernel image across virtual >> machines, resulting in better RAM and cache usage. > > That is something we wanna look into :) > It is, but that is a second order thing... especially since the x86 kernel makes heavy use of self-patching at the moment. What would be more significant, though, would be to avoid the memcpy() and instead decode the uncompressed kernel in-place. -hpa