public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Why XIP memory for variable storage?
Date: Fri, 16 Feb 2018 08:15:44 +0000	[thread overview]
Message-ID: <DB5PR04MB099848D4095FA88CF617F97D8ECB0@DB5PR04MB0998.eurprd04.prod.outlook.com> (raw)

Hi,


I want to implement Secure Uefi for my SoC and was looking for how keys and database were stored in edk2.

What i understood from the code is:
1.  We are using same memory space for storage of Secure and Non-Secure variables.
2.  We are assuming memory to be of XIP type.


Please help if above statements are correct and 
I want to use different memories for Secure and Non-Secure variables, 
e.g. i want my secure variables to be managed by my software running in EL3 or say a different memory which is not an XIP.


Is something similar exist in edk2 which i can refer?
Is any particular reason behind using XIP memory for variable storage?


Please help.


Thanks & Regards,
Meenakshi


                 reply	other threads:[~2018-02-16  8:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list 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=DB5PR04MB099848D4095FA88CF617F97D8ECB0@DB5PR04MB0998.eurprd04.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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