linux-kernel - Re: [RFC] x86 XIP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150323080713.GB25620@gmail.com>
Date:	Mon, 23 Mar 2015 09:07:14 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Jim Kukunas <james.t.kukunas@...ux.intel.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	tom.zanussi@...ux.intel.com,
	Arjan van de Ven <arjan@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...or.com>, tglx@...utronix.de,
	mingo@...hat.com, x86@...nel.org
Subject: Re: [RFC] x86 XIP

* Jim Kukunas <james.t.kukunas@...ux.intel.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/