From: Jim Kukunas <james.t.kukunas@linux.intel.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, tom.zanussi@linux.intel.com
Cc: Arjan van de Ven <arjan@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org
Subject: [PATCH 01/11] x86/xip: add XIP_KERNEL and XIP_BASE options
Date: Mon, 23 Mar 2015 00:46:30 -0700 [thread overview]
Message-ID: <1427096800-30452-2-git-send-email-james.t.kukunas@linux.intel.com> (raw)
In-Reply-To: <1427096800-30452-1-git-send-email-james.t.kukunas@linux.intel.com>
The CONFIG_XIP_KERNEL Kconfig option enables eXecute-In-Place
(XIP) support. When XIP_KERNEL is set, XIP_BASE points to the
physical address of the vmlinux ELF file.
Signed-off-by: Jim Kukunas <james.t.kukunas@linux.intel.com>
---
arch/x86/Kconfig | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index b7d31ca..f5fa02c 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -294,6 +294,25 @@ config ZONE_DMA
If unsure, say Y.
+config XIP_KERNEL
+ bool "eXecute-In-Place (XIP) support" if (X86_32 && EXPERT && EMBEDDED)
+ depends on !MODULES && !X86_PAE && !SMP
+ default n
+ help
+ With this option enabled, the text and any read-only segments of
+ the kernel are not copied from their initial location to their usual
+ location in RAM. As a result, when the kernel is located in storage
+ that is addressable by the CPU, the kernel text and read-only data
+ segments are never loaded into memory, thereby using less RAM.
+
+ Only enable this option if you know what you're doing.
+
+config XIP_BASE
+ hex "Physical address of XIP kernel" if XIP_KERNEL
+ default "0xFF800000"
+ help
+ The physical address for the beginning of the vmlinux file.
+
config SMP
bool "Symmetric multi-processing support"
---help---
--
2.1.0
next prev parent reply other threads:[~2015-03-23 7:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 7:46 [RFC] x86 XIP Jim Kukunas
2015-03-23 7:46 ` Jim Kukunas [this message]
2015-03-23 7:46 ` [PATCH 02/11] x86/xip: Update address of sections in linker script Jim Kukunas
2015-03-23 7:46 ` [PATCH 03/11] x86/xip: copy writable sections into RAM Jim Kukunas
2015-03-23 7:46 ` [PATCH 04/11] x86/xip: XIP boot trampoline page tables Jim Kukunas
2015-03-23 7:46 ` [PATCH 05/11] x86/xip: reserve memblock for only data Jim Kukunas
2015-03-23 7:46 ` [PATCH 06/11] x86/xip: after paging trampoline, discard PMDs above _brk Jim Kukunas
2015-03-23 7:46 ` [PATCH 07/11] x86/xip: make e820_add_kernel_range() a NOP Jim Kukunas
2015-03-23 7:46 ` [PATCH 08/11] x86/xip: in setup_arch(), handle resource physical addr Jim Kukunas
2015-03-23 7:46 ` [PATCH 09/11] x86/xip: snip the kernel text out of the memory mapping Jim Kukunas
2015-03-23 7:46 ` [PATCH 10/11] x86/xip: resolve alternative instructions at build Jim Kukunas
2015-03-23 8:33 ` Borislav Petkov
2015-03-23 8:38 ` Borislav Petkov
2015-03-25 0:50 ` Jim Kukunas
2015-03-25 8:44 ` Borislav Petkov
2015-03-23 22:40 ` Paul Bolle
2015-03-23 7:46 ` [PATCH 11/11] x86/xip: update _va() and _pa() macros Jim Kukunas
2015-03-23 8:09 ` Ingo Molnar
2015-03-23 15:09 ` Borislav Petkov
2015-03-23 8:07 ` [RFC] x86 XIP Ingo Molnar
2015-03-25 0:14 ` Jim Kukunas
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=1427096800-30452-2-git-send-email-james.t.kukunas@linux.intel.com \
--to=james.t.kukunas@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=x86@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®