From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752093AbbCWIHV (ORCPT ); Mon, 23 Mar 2015 04:07:21 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:37166 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752002AbbCWIHS (ORCPT ); Mon, 23 Mar 2015 04:07:18 -0400 Date: Mon, 23 Mar 2015 09:07:14 +0100 From: Ingo Molnar To: Jim Kukunas Cc: Linux Kernel , tom.zanussi@linux.intel.com, Arjan van de Ven , "H. Peter Anvin" , tglx@linutronix.de, mingo@redhat.com, x86@kernel.org Subject: Re: [RFC] x86 XIP Message-ID: <20150323080713.GB25620@gmail.com> References: <1427096800-30452-1-git-send-email-james.t.kukunas@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1427096800-30452-1-git-send-email-james.t.kukunas@linux.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jim Kukunas wrote: > > Hi Folks, > > This patchset introduces eXecute-In-Place (XIP) support for x86. > [...] So we'd need a lot better high level description than this: - a bit of background description: what are the advantages of having the kernel image in non-RAM (flash), etc. - on what hardware/bootloaders is or will be XIP supported? Also, there should probably be some fail-safe mechanism included: such as to check whether caching attributes (MTRRs, PAT) are properly set for the XIP area (at minimum to not be uncacheable). Thanks, Ingo