From: "Vincent Stehlé" <v-stehle@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 3/3] ARM: OMAP5: redefine arm_setup_identity_mapping
Date: Tue, 8 Jan 2013 13:27:56 +0100 [thread overview]
Message-ID: <50EC10CC.3030609@ti.com> (raw)
In-Reply-To: <50EBFFAE.1090402@ti.com>
On 01/08/2013 12:14 PM, R Sricharan wrote:
(..)
> We had this problem of speculative aborts in the kernel uncompress code
> as well, which maps all of 4GB address space. It was solved by setting
> the non-DRAM region as non-executable(XN) and with client permissions
> to the domain in the DACR register.
>
> This way speculative prefetches are avoided not only to the page 0,
> but also to other read sensitive I/O regions.
>
> I have created a similar patch in u-boot and posted a RFC now.
> I was using your first patch [1] and rest from me.
(..)
>
> Please let me know your take on that.
Hi Sricharan,
Your solution to this issue looks more elegant to me than my unmapping
page 0 completely.
I tested your patches and they work for me on both GP (without
security) and EMU (with security) OMAP5 ES1.0 devices. I'll keep them,
thanks :) You can add my 'Tested-by' if you want:
Tested-by: Vincent Stehl? <v-stehle@ti.com>
Best regards,
V.
next prev parent reply other threads:[~2013-01-08 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <92476020c6e1ef888207ca6f661c48068050efbf>
2013-01-07 14:44 ` [U-Boot] Update OMAP5 "unmap first page" patch series Vincent Stehlé
2013-01-07 14:44 ` [U-Boot] [PATCH v4 1/3] ARM: cache: declare set_section_dcache Vincent Stehlé
2013-01-07 14:44 ` [U-Boot] [PATCH v4 2/3] ARM: cache: introduce weak arm_setup_identity_mapping Vincent Stehlé
2013-01-07 14:44 ` [U-Boot] [PATCH v4 3/3] ARM: OMAP5: redefine arm_setup_identity_mapping Vincent Stehlé
2013-01-08 11:14 ` R Sricharan
2013-01-08 12:27 ` Vincent Stehlé [this message]
2013-01-08 13:05 ` R Sricharan
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=50EC10CC.3030609@ti.com \
--to=v-stehle@ti.com \
--cc=u-boot@lists.denx.de \
/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.