public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 1/2] Reserve secure memory
Date: Tue, 15 Dec 2015 09:02:04 +0800	[thread overview]
Message-ID: <566F668C.5070007@freescale.com> (raw)
In-Reply-To: <1449259028-9148-2-git-send-email-yorksun@freescale.com>



On 12/05/2015 03:57 AM, 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. This is different from PRAM
> used to reserve private memory. PRAM offers memory at the top
> of u-boot memory, not necessarily the real end of memory for
> systems with very large DDR. Using the end of memory simplifies
> MMU setup and avoid memory fragmentation.
> 
> "bdinfo" command shows gd->secure_ram value if this memory is
> marked as secured.
> 
> Signed-off-by: York Sun <yorksun@freescale.com>
> 
> ---
> 
> Changes in v7: None
> Changes in v6:
>   Move cmd_bdinfo change into this patch
>   Move flag macros and comments of secure_ram into this patch
> 
> Changes in v5: None
> Changes in v4: None
> Changes in v3:
>   Put ifdef around secure_ram
>   Move defining CONFIG_SYS_MEM_RESERVE_SECURE to patch 2/2
> 
> Changes in v2:
>   Do not use CONFIG_SYS_MEM_TOP_HIDE mechanism
> 
> Changes in v1:
>   Initial patch.
>   Depends on http://patchwork.ozlabs.org/patch/540248/
> 

Applied to fsl-qoriq master. Awaiting upstream.

York

  reply	other threads:[~2015-12-15  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 19:57 [U-Boot] [PATCH v7 0/2] Make most DDR non-secure in MMU while keep a small block secure York Sun
2015-12-04 19:57 ` [U-Boot] [PATCH v7 1/2] Reserve secure memory York Sun
2015-12-15  1:02   ` York Sun [this message]
2015-12-04 19:57 ` [U-Boot] [PATCH v7 2/2] armv8: fsl-layerscape: Make DDR non secure in MMU tables York Sun
2015-12-15  1:02   ` 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=566F668C.5070007@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