From: Sami Mujawar <Sami.Mujawar@arm.com>
To: Sudeep Holla <Sudeep.Holla@arm.com>,
Bharat Kumar Gogada <bharatku@xilinx.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>
Subject: Re: ACPI flow for reserved memory
Date: Mon, 7 Mar 2022 17:49:23 +0000 [thread overview]
Message-ID: <D676ADF1-33F3-47A2-932F-40F01D602787@arm.com> (raw)
In-Reply-To: <YiJI4fe0tYDj96ob@bogus>
Hi Bharat,
The UEFI specification version 2.9, section 7.2 Memory Allocation Services, EFI_BOOT_SERVICES.GetMemoryMap(), page 172 states the following:
"... Regions that are backed by physical hardware, but are not supposed to be accessed by the OS, must be returned as EfiReservedMemoryType. ..."
This can be achieved by adding the memory region as Reserved Memory in the firmware.
Example:
Status = gDS->AddMemorySpace (
EfiGcdMemoryTypeReserved,
ReservedMemBase,
ReservedMemSize,
EFI_MEMORY_UC
);
if (EFI_ERROR (Status)) {
DEBUG ((
DEBUG_ERROR,
"Failed to add memory space. Status = %r\n",
Status
));
return Status;
}
Hope this helps. Please let me know if you have any further queries.
Regards,
Sami Mujawar
On 04/03/2022, 17:14, "Sudeep Holla" <sudeep.holla@arm.com> wrote:
Hi Bharat,
I am not UEFI expert but I was sure there would be some options for this.
Checking with Sami(cc-ed), confirmed the same.
On Thu, Mar 03, 2022 at 11:07:54AM +0000, Bharat Kumar Gogada wrote:
> Hi All,
>
> In device tree we have several ways to
> reserve memory (https://github.com/Xilinx/linux-xlnx/blob/master/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt).
>
> Can anyone please help equivalent flow for ACPI.
@Sami, please share any details you may have.
--
Regards,
Sudeep
prev parent reply other threads:[~2022-03-07 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 11:07 Bharat Kumar Gogada
2022-03-04 17:14 ` Sudeep Holla
2022-03-07 17:49 ` Sami Mujawar [this message]
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=D676ADF1-33F3-47A2-932F-40F01D602787@arm.com \
--to=sami.mujawar@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=bharatku@xilinx.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
/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
all inboxes | Powered by JetHome®