From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH 0/2] ShellPkg/memmap: Dump memory map information for all memory types
Date: Thu, 11 May 2017 18:27:04 +0800 [thread overview]
Message-ID: <20170511102706.89404-1-ruiyu.ni@intel.com> (raw)
The patch dumps memory map information for all memory types.
But to follow the SFO format of "memmap" defined in Shell 2.2 spec,
the patch doesn't dump the memory map information for OEM/OS
memory types. But it does include the OEM/OS memory in the total
size in SFO format.
Ruiyu Ni (2):
ShellPkg/memmap: Refine code
ShellPkg/memmap: Dump memory map information for all memory types
.../Library/UefiShellDebug1CommandsLib/MemMap.c | 199 +++++++++++++++------
.../UefiShellDebug1CommandsLib.uni | 4 +-
2 files changed, 148 insertions(+), 55 deletions(-)
--
2.12.2.windows.2
next reply other threads:[~2017-05-11 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 10:27 Ruiyu Ni [this message]
2017-05-11 10:27 ` [PATCH 1/2] ShellPkg/memmap: Refine code Ruiyu Ni
2017-05-11 10:27 ` [PATCH 2/2] ShellPkg/memmap: Dump memory map information for all memory types Ruiyu Ni
2017-05-11 16:23 ` [PATCH 0/2] " Carsey, Jaben
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=20170511102706.89404-1-ruiyu.ni@intel.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