From: Borislav Petkov <bp@alien8.de>
To: Jim Kukunas <james.t.kukunas@linux.intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
tom.zanussi@linux.intel.com,
Arjan van de Ven <arjan@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org
Subject: Re: [PATCH 10/11] x86/xip: resolve alternative instructions at build
Date: Wed, 25 Mar 2015 09:44:39 +0100 [thread overview]
Message-ID: <20150325084439.GA3291@pd.tnic> (raw)
In-Reply-To: <20150325005049.GB2600@jtk-ivb.jf.intel.com>
On Tue, Mar 24, 2015 at 05:50:49PM -0700, Jim Kukunas wrote:
> XIP isn't a general feature that distros are going to be enabling. It's
> designed for a very specific usage where people are building very custom
> kernels.
So something very very special which is not going to be enabled on
distros...
But it is touching main x86 code paths a good deal. We should think
about abstracting it out of the way. The current EFI ifdeffery is
already nasty and sprinkling #ifdef CONFIG_XIP_KERNEL in addition is
making it even worse. :/
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-03-25 8:46 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 ` [PATCH 01/11] x86/xip: add XIP_KERNEL and XIP_BASE options Jim Kukunas
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 [this message]
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=20150325084439.GA3291@pd.tnic \
--to=bp@alien8.de \
--cc=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.t.kukunas@linux.intel.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