From: Michael Zimmermann <sigmaepsilon92@gmail.com>
To: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: correct way to reserve memory from PrePi?
Date: Wed, 14 Dec 2016 11:02:43 +0100 [thread overview]
Message-ID: <CAN9vWDJ+1Ti69tFmEWo+z__f6aTGmpXGLhcTXEmeNOt8SAi1NQ@mail.gmail.com> (raw)
I tried both BuildResourceDescriptorHob and BuildMemoryAllocationHob
but apparently they don't have any effect.
When I look at the output of the shell's memmap command there aren't
any reserved/unavailable pages.
Furthermore, when using AllocatePages with one of the physical
addresses which I've reserved it succeeds which means that it's not
just a problem of how the memmap command works.
Am I doing something wrong or is this a bug?
Thanks
Michael
next reply other threads:[~2016-12-14 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 10:02 Michael Zimmermann [this message]
2016-12-14 10:21 ` correct way to reserve memory from PrePi? Ard Biesheuvel
2016-12-14 15:13 ` Michael Zimmermann
2016-12-14 17:57 ` Michael Zimmermann
2016-12-15 4:55 ` Gao, Liming
2016-12-15 5:02 ` Michael Zimmermann
2016-12-15 5:12 ` Gao, Liming
2016-12-15 5:27 ` Michael Zimmermann
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=CAN9vWDJ+1Ti69tFmEWo+z__f6aTGmpXGLhcTXEmeNOt8SAi1NQ@mail.gmail.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