public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Sakar Arora <sakar.arora@nxp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Exporting discontiguous System Memory to EFI STUB
Date: Thu, 15 Sep 2016 08:45:10 +0000	[thread overview]
Message-ID: <VI1PR04MB21733363A608B9F048849E8AF8F00@VI1PR04MB2173.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB2173B4CEB9AB3ED7B4DAEC93F8F00@VI1PR04MB2173.eurprd04.prod.outlook.com>

Hi

This is in aarch64 UEFI context.

The efi stub code ignores any memory nodes in the device tree. It only relies on the UEFI memory map for memory info.

In such a scenario, how can one export discontiguous regions of system memory to the efi stub? There seems to be only one way to inform UEFI about system memory, via PcdSystemMemoryBase.

Looking at the latest Arm Juno code, it seems like building a memory resource descriptor hob, for the extra memory region, does the trick. Would that be the best way to go?

Suggestions please.

Thanks,
Sakar


       reply	other threads:[~2016-09-15  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR04MB2173B4CEB9AB3ED7B4DAEC93F8F00@VI1PR04MB2173.eurprd04.prod.outlook.com>
2016-09-15  8:45 ` Sakar Arora [this message]
2016-09-15  9:01   ` Exporting discontiguous System Memory to EFI STUB Laszlo Ersek
2016-09-15 11:31     ` Ard Biesheuvel
2016-09-21  9:10       ` Bhupesh Sharma
2016-09-21 11:17         ` Laszlo Ersek
2016-09-21 11:20           ` Ard Biesheuvel
2016-09-21 11:32             ` Laszlo Ersek
2016-09-21 11:32             ` Bhupesh Sharma
2016-09-21 11:36               ` Ard Biesheuvel

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=VI1PR04MB21733363A608B9F048849E8AF8F00@VI1PR04MB2173.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