From: Catalin Marinas <catalin.marinas@arm.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
R Sricharan <r.sricharan@ti.com>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space.
Date: Tue, 8 May 2012 15:16:31 +0100 [thread overview]
Message-ID: <20120508141631.GG17798@arm.com> (raw)
In-Reply-To: <CAMQu2gxXB4GyddjrcKWwJ=KXx=MoDs7DdwhbOY85qkVJ1Vv3wA@mail.gmail.com>
On Tue, May 08, 2012 at 03:01:57PM +0100, Shilimkar, Santosh wrote:
> From b906ef372f0e2dfa7e1fbc3c87406b1c303d8975 Mon Sep 17 00:00:00 2001
> From: R Sricharan <r.sricharan@ti.com>
> Date: Mon, 7 May 2012 15:11:58 +0530
> Subject: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address
> space.
>
> ARM decompressor code setups entire 4GB address space pages.
> Out of the 4GB, about 256MB are setup with normal memory attributes
> for needed DRAM and the rest of the address space as Strongly ordered.
>
> But since all the sections are mapped in DOMAIN0(Manager), processor
> like Cortex-A15, can speculatively prefetch from non-DRAM read sensitive
> areas even in the presence of XN(Non-executable). This is because XN
> attribute is ignored when domain is Manager.
>
> This can lead to accesses to non-accessible address regions leading
> to various interconnect violations. The issue is observed on OMAP5.
>
> This patch tries to fix the issue by ensuring that all regions
> are marked as a client domain so that XN attribute is effective.
>
> Signed-off-by: R Sricharan <r.sricharan@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm/boot/compressed/head.S | 10 ++++++++--
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/compressed/head.S b/arch/arm/boot/compressed/head.S
> index dc7e8ce..a2602b8 100644
> --- a/arch/arm/boot/compressed/head.S
> +++ b/arch/arm/boot/compressed/head.S
> @@ -578,10 +578,12 @@ __setup_mmu: sub r3, r4, #16384 @ Page directory size
> mov r9, r0, lsr #18
> mov r9, r9, lsl #18 @ start of RAM
> add r10, r9, #0x10000000 @ a reasonable RAM size
> - mov r1, #0x12
> + mov r1, #0x02 @ Default executable section
I think it is simpler if you leave the original code here (with XN)
> orr r1, r1, #3 << 10
> add r2, r3, #16384
> 1: cmp r1, r9 @ if virt > start of RAM
> + orrlo r1, r1, #0x10 @ Mark XN for non DRAM
> + bichs r1, r1, #0x10 @ clear XN for DRAM
and just do the bichs above.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space.
Date: Tue, 8 May 2012 15:16:31 +0100 [thread overview]
Message-ID: <20120508141631.GG17798@arm.com> (raw)
In-Reply-To: <CAMQu2gxXB4GyddjrcKWwJ=KXx=MoDs7DdwhbOY85qkVJ1Vv3wA@mail.gmail.com>
On Tue, May 08, 2012 at 03:01:57PM +0100, Shilimkar, Santosh wrote:
> From b906ef372f0e2dfa7e1fbc3c87406b1c303d8975 Mon Sep 17 00:00:00 2001
> From: R Sricharan <r.sricharan@ti.com>
> Date: Mon, 7 May 2012 15:11:58 +0530
> Subject: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address
> space.
>
> ARM decompressor code setups entire 4GB address space pages.
> Out of the 4GB, about 256MB are setup with normal memory attributes
> for needed DRAM and the rest of the address space as Strongly ordered.
>
> But since all the sections are mapped in DOMAIN0(Manager), processor
> like Cortex-A15, can speculatively prefetch from non-DRAM read sensitive
> areas even in the presence of XN(Non-executable). This is because XN
> attribute is ignored when domain is Manager.
>
> This can lead to accesses to non-accessible address regions leading
> to various interconnect violations. The issue is observed on OMAP5.
>
> This patch tries to fix the issue by ensuring that all regions
> are marked as a client domain so that XN attribute is effective.
>
> Signed-off-by: R Sricharan <r.sricharan@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm/boot/compressed/head.S | 10 ++++++++--
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/compressed/head.S b/arch/arm/boot/compressed/head.S
> index dc7e8ce..a2602b8 100644
> --- a/arch/arm/boot/compressed/head.S
> +++ b/arch/arm/boot/compressed/head.S
> @@ -578,10 +578,12 @@ __setup_mmu: sub r3, r4, #16384 @ Page directory size
> mov r9, r0, lsr #18
> mov r9, r9, lsl #18 @ start of RAM
> add r10, r9, #0x10000000 @ a reasonable RAM size
> - mov r1, #0x12
> + mov r1, #0x02 @ Default executable section
I think it is simpler if you leave the original code here (with XN)
> orr r1, r1, #3 << 10
> add r2, r3, #16384
> 1: cmp r1, r9 @ if virt > start of RAM
> + orrlo r1, r1, #0x10 @ Mark XN for non DRAM
> + bichs r1, r1, #0x10 @ clear XN for DRAM
and just do the bichs above.
--
Catalin
next prev parent reply other threads:[~2012-05-08 14:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 13:42 [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space Santosh Shilimkar
2012-05-07 13:42 ` Santosh Shilimkar
2012-05-08 12:41 ` Catalin Marinas
2012-05-08 12:41 ` Catalin Marinas
2012-05-08 14:01 ` Shilimkar, Santosh
2012-05-08 14:01 ` Shilimkar, Santosh
2012-05-08 14:16 ` Catalin Marinas [this message]
2012-05-08 14:16 ` Catalin Marinas
2012-05-08 14:20 ` Santosh Shilimkar
2012-05-08 14:20 ` Santosh Shilimkar
2012-05-08 14:23 ` Catalin Marinas
2012-05-08 14:23 ` Catalin Marinas
2012-05-08 14:43 ` Santosh Shilimkar
2012-05-08 14:43 ` Santosh Shilimkar
2012-05-08 21:55 ` Russell King - ARM Linux
2012-05-08 21:55 ` Russell King - ARM Linux
2012-05-09 8:50 ` Shilimkar, Santosh
2012-05-09 8:50 ` Shilimkar, Santosh
2012-05-09 10:23 ` Catalin Marinas
2012-05-09 10:23 ` Catalin Marinas
2012-05-09 12:23 ` Russell King - ARM Linux
2012-05-09 12:23 ` Russell King - ARM Linux
2012-05-09 12:30 ` Shilimkar, Santosh
2012-05-09 12:30 ` Shilimkar, Santosh
2012-05-09 15:48 ` Russell King - ARM Linux
2012-05-09 15:48 ` Russell King - ARM Linux
2012-05-09 20:44 ` Buckley, Bryan
2012-05-09 20:44 ` Buckley, Bryan
2012-05-09 21:40 ` Russell King - ARM Linux
2012-05-09 21:40 ` Russell King - ARM Linux
2012-05-15 18:55 ` Buckley, Bryan
2012-05-15 18:55 ` Buckley, Bryan
2012-05-10 7:11 ` Santosh Shilimkar
2012-05-10 7:11 ` Santosh Shilimkar
2012-05-10 8:53 ` Russell King - ARM Linux
2012-05-10 8:53 ` Russell King - ARM Linux
2012-05-10 9:41 ` Santosh Shilimkar
2012-05-10 9:41 ` Santosh Shilimkar
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=20120508141631.GG17798@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=r.sricharan@ti.com \
--cc=santosh.shilimkar@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.