[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZpAqmnS5=F9va6xWECmG85TO_Lv7Gicx5qx=m6bNgohw@mail.gmail.com>
Date: Wed, 23 Oct 2013 16:11:46 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Russ Dill <Russ.Dill@...com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Linux-OMAP <linux-omap@...r.kernel.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, mans@...sr.com,
Shawn Guo <shawn.guo@...aro.org>,
Dave Martin <Dave.Martin@....com>,
Russell King - ARM Linux <linux@....linux.org.uk>
Subject: Re: [RFC PATCH 00/11] Embeddable Position Independent Executable
On Tue, Sep 17, 2013 at 2:43 PM, Russ Dill <Russ.Dill@...com> wrote:
> This patch adds support for and demonstrates the usage of an embedded
> position independent executable (PIE). The goal is to allow the use of C
> code in situations where carefully written position independent assembly
> was previously required.
This is perfectly applicable to the ARM TCM memory as well.
Currently we have arch/arm/kernel/tcm.c and related extensions to
kernel/vmlinux.kds.S, which enables us to tag some certain code
to be compiled into TCM memory which we map statically to
0xfffe0000 thru 0xfffeffff, but this is a better approach, especially
nice since it is the solution to the multiplatform situation, as we
need to select to copy code into that memory only on the specific
target.
I'll try to have a deeper look at this, please keep me on CC for
this series.
Yours,
Linus Walleij
--
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/
Powered by blists - more mailing lists