From: "Jianyong Wu" <jianyong.wu@arm.com>
To: devel@edk2.groups.io, Sami.Mujawar@arm.com
Cc: ard.biesheuvel@linaro.org, justin.he@arm.com, jianyong.wu@arm.com
Subject: [PATCH 0/2] CloudHv/arm: Add specific mem info lib
Date: Fri, 29 Jul 2022 15:21:44 +0800 [thread overview]
Message-ID: <20220729072146.169750-1-jianyong.wu@arm.com> (raw)
Currently, the meminfo lib for CloudHv/arm is reusing QEMU's. As the memory
layout for cloud hypervisor is changed, it needs a new meminfo lib.
Signed-off-by: Jianyong Wu <jianyong.wu@arm.com>
Jianyong Wu (2):
CloudHv/arm: add PeiMemInfoLib
CloudHv/arm: switch PeiMemLib to its own
ArmVirtPkg/ArmVirtCloudHv.dsc | 2 +-
.../CloudHvVirtMemInfoLib.c | 251 ++++++++++++++++++
.../CloudHvVirtMemInfoPeiLib.inf | 46 ++++
3 files changed, 298 insertions(+), 1 deletion(-)
create mode 100755 ArmVirtPkg/Library/CloudHvVirtMemInfoLib/CloudHvVirtMemInfoLib.c
create mode 100755 ArmVirtPkg/Library/CloudHvVirtMemInfoLib/CloudHvVirtMemInfoPeiLib.inf
--
2.17.1
next reply other threads:[~2022-07-29 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 7:21 Jianyong Wu [this message]
2022-07-29 7:21 ` [PATCH 1/2] CloudHv/arm: add PeiMemInfoLib Jianyong Wu
2022-08-08 11:27 ` Sami Mujawar
2022-08-09 8:31 ` Jianyong Wu
[not found] ` <1709A00AB94047B2.29555@groups.io>
2022-08-18 5:22 ` [edk2-devel] " Jianyong Wu
2022-08-18 11:40 ` Sami Mujawar
2022-08-19 7:41 ` Jianyong Wu
2022-07-29 7:21 ` [PATCH 2/2] CloudHv/arm: switch PeiMemLib to its own Jianyong Wu
2022-08-08 11:29 ` Sami Mujawar
[not found] ` <17063BDF40129601.5552@groups.io>
2022-08-08 7:03 ` [edk2-devel] [PATCH 1/2] CloudHv/arm: add PeiMemInfoLib Jianyong Wu
[not found] ` <17063BDFB8173BFA.24450@groups.io>
2022-08-08 7:04 ` [edk2-devel] [PATCH 2/2] CloudHv/arm: switch PeiMemLib to its own Jianyong Wu
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=20220729072146.169750-1-jianyong.wu@arm.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