From: "H. Peter Anvin" <hpa@zytor.com>
To: Chao Peng <chao.p.peng@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>, Michal Marek <mmarek@suse.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Kees Cook <keescook@chromium.org>, Baoquan He <bhe@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Paul Bolle <pebolle@tiscali.nl>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Borislav Petkov <bp@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
"David S. Miller" <davem@davemloft.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Garnier <thgarnie@google.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Tejun Heo <tj@kernel.org>, Daniel Mack <daniel@zonque.org>,
Helge Deller <deller@gmx.de>, Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] x86/boot: Support uncompressed kernel
Date: Tue, 28 Mar 2017 15:38:49 -0700 [thread overview]
Message-ID: <3cbfa24b-8bae-7cc9-dcf5-93f02971e673@zytor.com> (raw)
In-Reply-To: <1490702482.3011.7.camel@linux.intel.com>
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
next prev parent reply other threads:[~2017-03-28 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 12:51 Chao Peng
2017-03-23 15:07 ` Yinghai Lu
2017-03-23 15:31 ` Sergey Senozhatsky
2017-03-24 5:35 ` Chao Peng
2017-03-27 7:58 ` Sebastian Andrzej Siewior
2017-03-27 9:25 ` Chao Peng
2017-03-27 11:47 ` Michal Marek
2017-03-27 13:25 ` Arnd Bergmann
2017-03-28 12:01 ` Chao Peng
2017-03-28 22:38 ` H. Peter Anvin [this message]
2017-03-28 22:55 ` Andy Lutomirski
2017-03-24 8:09 ` Michal Marek
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=3cbfa24b-8bae-7cc9-dcf5-93f02971e673@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=bp@suse.de \
--cc=chao.p.peng@linux.intel.com \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=hjl.tools@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=nicolas.pitre@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pebolle@tiscali.nl \
--cc=pmladek@suse.com \
--cc=riel@redhat.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®