From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings!
Date: Fri, 1 Mar 2013 09:21:50 -0500 [thread overview]
Message-ID: <5130B97E.5040308@ti.com> (raw)
In-Reply-To: <20130301084504.6df4b793@lilith>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/01/2013 02:45 AM, Albert ARIBAUD wrote:
> Hi Sricharan,
>
> On Fri, 1 Mar 2013 09:57:25 +0530, Sricharan R
> <r.sricharan@ti.com> wrote:
>
>> Hi Albert,
>>
>> On Thursday 28 February 2013 08:35 PM, Albert ARIBAUD wrote:
>>> On Thu, 28 Feb 2013 15:20:44 +0100, Albert ARIBAUD
>>> <albert.u.boot@aribaud.net> wrote:
>>>
>>>> (sorry for any duplicate of this mail)
>>>>
>>>> Hi R Sricharan,
>>>>
>>>> On Tue, 8 Jan 2013 23:38:22 +0530, R
>>>> Sricharan<r.sricharan@ti.com> wrote:
>>>>
>>>>> Currently for ARM based cpu's, mmu pagetable attributes are
>>>>> set with manager permissions for all 4GB address space.
>>>>> Because of this the 'execute never (XN)' permission is
>>>>> never checked on read sensitive regions which results in
>>>>> speculative aborts.
>>>>>
>>>>> This series changes the domain permissions of the full 4GB
>>>>> space to client access for OMAP socs. This avoids all the
>>>>> speculative aborts that are currently seen on OMAP5 secure
>>>>> devices.
>>>>>
>>>>> Tested on OMAP5 SDP (HS) soc.
>>>>>
>>>>> This series depends on [1] the patch sent by <Vincent
>>>>> Stehle<v-stehle@ti.com>
>>>>>
>>>>> [1]
>>>>> http://www.mail-archive.com/u-boot at lists.denx.de/msg102709.html
>>>>>
>>>>>
>>>>>
R Sricharan (2):
>>>>> ARM: mmu: Introduce weak dram_bank_setup function ARM: mmu:
>>>>> Set domain permissions to client access
>>>>>
>>>>> arch/arm/cpu/armv7/cache_v7.c | 3 ++
>>>>> arch/arm/cpu/armv7/omap-common/hwinit-common.c | 35
>>>>> ++++++++++++++++++++++++ arch/arm/include/asm/cache.h
>>>>> | 1 + arch/arm/include/asm/system.h |
>>>>> 14 ++++++++++ arch/arm/lib/cache-cp15.c
>>>>> | 13 ++++++++- 5 files changed, 65 insertions(+), 1
>>>>> deletion(-)
>>>>>
>>>> Series applied to u-boot-arm/master, thanks!
>>> Correction: I'd wrongly inferred from the testing done on OMAP5
>>> that the series would build fine. However it appears that for
>>> targets omap4_sdp4430, omap4_panda and omap5_evm, patch 2/2 has
>>> warnings:
>>>
>>> hwinit-common.c: In function 'dram_bank_mmu_setup':
>>> hwinit-common.c:279:3: warning: implicit declaration of
>>> function 'set_section_dcache'
>>> [-Wimplicit-function-declaration]
>>>
>>> Luckily, I had not committed to the git repo yet.
>>>
>>> R Sicharan, can you please check and fix this warning?
>>>
>>> Amicalement,
>> Oh, thats because as i mentioned above, it depends on the below
>> patch from vincent .
>>
>> http://www.mail-archive.com/u-boot at lists.denx.de/msg102709.html
>>
>> I did not repost it though. I will do it now for clarity.
>
> Ok -- Vincent's patch was not in my Patchwork TODO and I had read
> patches 1/2 and 2/2 in Patchwork, but I had not read the cover
> letter thoroughly enough so I had missed the dependency.
>
> (Cc:ing Vincent and Tom)
>
> Vincent's patch series is delegated to Tom and marked "superseded"
> in Patchwork but I don't see any later, superseding, series. What
> can/should I make of it?
It's possible I mis-read things and it shouldn't be superseded. Can
you list all of the patches that Albert should apply please? Thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRMLl9AAoJENk4IS6UOR1WPX4P+wRRwsSgPm5edbbBN/TkBi6a
x1LIMEKYC2QN73ea8czz4oeOR76MXidQUdYRmimJ2qzYRaEq9Y9ulFjIs0zc/6Gu
ydnO4eeb8keU27ItlmKubnEOwsev/wtZNIQhvwJJNvuSiG9rBvKAGDh9L8UQrq3t
cwhqWpNhL4isoYG/rB2BDHKrwB62DboOzmaNHACpVaCZNg606QH+eHnget1CWBCD
p2O88TSkOVoQHVAj76mdgm8+9WE/mlqn5h4RUU81U3DHiAuTDg0N+J1IJPd3zjhP
86zvj1q4i3JuZySg+IdxouiPTqnw88ZYJ2XHtQvAeDGr5Q680Gb1k18vMIRGlNtv
AVx9ipQHaOFXSbTQzlmTNT4EutseaGVa5Ioj3vUkRozBONIfuDmEZAnE+YXFfgQV
OQZzidbWLOSFbfDPSi6XMUgtXVEtUPP6eGPV0sv5HUvfYr+3zUMtFwdGqe47X1lC
z5V1xpug2mOvU0+6l1nO1egxdRM1JlHroV33oRBXMFoUZUowpobGWeJubjw7WB86
39qoR4xwnyPup3+HHlKVBXmRg6j7jayOUdU0o69kJYO7M0QB/CjADePpSDTrcb9n
lkk5KSYVQRzbOar7n9J6jiYoL5WFdj7uSCLpfQ5u/b26r/U2I/YGWPj/w6oGR9+v
+3tp/XeRDuXUQkplQEd7
=jW2y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-01 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 18:08 [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access R Sricharan
2013-01-08 18:08 ` [U-Boot] [PATCH 1/2] ARM: mmu: Introduce weak dram_bank_setup function R Sricharan
2013-01-08 18:08 ` R Sricharan
2013-01-08 18:08 ` [U-Boot] [PATCH 2/2] ARM: mmu: Set domain permissions to client access R Sricharan
2013-02-03 14:17 ` [U-Boot] [PATCH 0/2] " Albert ARIBAUD
2013-02-03 14:19 ` R Sricharan
2013-02-03 14:22 ` R Sricharan
2013-02-03 15:25 ` Albert ARIBAUD
2013-02-03 16:13 ` R Sricharan
2013-02-28 14:20 ` Albert ARIBAUD
2013-02-28 15:05 ` [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings! Albert ARIBAUD
2013-03-01 4:27 ` Sricharan R
2013-03-01 4:59 ` [U-Boot] [PATCH RESEND] ARM: cache: declare set_section_dcache Sricharan R
2013-03-01 7:45 ` [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings! Albert ARIBAUD
2013-03-01 14:21 ` Tom Rini [this message]
2013-03-02 10:08 ` R, Sricharan
2013-03-02 22:46 ` Albert ARIBAUD
2013-03-04 10:08 ` Vincent Stehlé
2013-03-05 6:04 ` [U-Boot] [PATCH RESEND 0/3] ARM: mmu: Set domain permissions to client access Sricharan R
2013-03-05 6:04 ` [U-Boot] [PATCH RESEND 1/3] ARM: cache: declare set_section_dcache Sricharan R
2013-03-05 6:04 ` [U-Boot] [PATCH RESEND 2/3] ARM: mmu: Introduce weak dram_bank_setup function Sricharan R
2013-03-05 6:04 ` [U-Boot] [PATCH RESEND 3/3] ARM: mmu: Set domain permissions to client access Sricharan R
2013-03-12 4:44 ` [U-Boot] [PATCH RESEND 0/3] " Sricharan R
2013-03-28 8:44 ` Albert ARIBAUD
2013-03-05 6:39 ` [U-Boot] [PATCH 0/2] ARM: mmu: Set domain permissions to client access - build warnings! Sricharan R
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=5130B97E.5040308@ti.com \
--to=trini@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.