From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/2] Reserve secure memory
Date: Mon, 16 Nov 2015 09:24:11 -0800 [thread overview]
Message-ID: <564A113B.4090709@freescale.com> (raw)
In-Reply-To: <1447693914.7686.84.camel@infinera.com>
On 11/16/2015 09:11 AM, Joakim Tjernlund wrote:
> On Mon, 2015-11-16 at 08:34 -0800, York Sun wrote:
>> Secure memory is at the end of memory, separated and reserved
>> from OS, tracked by gd->secure_ram. Secure memory can host
>> MMU tables, security monitor, etc.
>
> Don't see the difference with pram here?
> Also, do you really wan't to hide the memory from Linux or will
> a resv map do? You get a lot of small TLB maps if memory is non power of 2
>
Jocke,
It is different from pram. First, it is at the end of memory, not the top of
u-boot memory. The difference is where u-boot runs in memory. Second, the size
is much bigger, even this patch doesn't limit the size. In my system, I reserve
2MB memory.
Since we already have CONFIG_SYS_MEM_TOP_HIDE, I think it is a good way to
reserve big chunk of memory without fragmentation. In my system, the end of
usable memory is aligned with 512MB.
York
next prev parent reply other threads:[~2015-11-16 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:34 [U-Boot] [PATCH v4 0/2] Make most DDR non-secure in MMU while keep a small block secure York Sun
2015-11-16 16:34 ` [U-Boot] [PATCH v4 1/2] Reserve secure memory York Sun
2015-11-16 17:11 ` Joakim Tjernlund
2015-11-16 17:24 ` York Sun [this message]
2015-11-16 16:34 ` [U-Boot] [PATCH v4 2/2] armv8: fsl-layerscape: Make DDR non secure in MMU tables York Sun
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=564A113B.4090709@freescale.com \
--to=yorksun@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox