public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jianyong Wu" <jianyong.wu@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Sami Mujawar <Sami.Mujawar@arm.com>
Cc: "ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	Justin He <Justin.He@arm.com>, Jianyong Wu <Jianyong.Wu@arm.com>
Subject: Re: [PATCH v2 0/2] CloudHv/arm: Add specific mem info lib
Date: Thu, 25 Aug 2022 07:29:16 +0000	[thread overview]
Message-ID: <DB9PR08MB7511B5EDC2404D932581EE3DF4729@DB9PR08MB7511.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20220819080911.188127-1-jianyong.wu@arm.com>

Ping ...
Any comments?

Thanks
Jianyong
> -----Original Message-----
> From: Jianyong Wu <jianyong.wu@arm.com>
> Sent: Friday, August 19, 2022 4:09 PM
> To: devel@edk2.groups.io; Sami Mujawar <Sami.Mujawar@arm.com>
> Cc: ardb+tianocore@kernel.org; Justin He <Justin.He@arm.com>; Jianyong
> Wu <Jianyong.Wu@arm.com>
> Subject: [PATCH v2 0/2] CloudHv/arm: Add specific mem info lib
>
> 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                   | 230 ++++++++++++++++++
>  .../CloudHvVirtMemInfoLib.h                   |  42 ++++
>  .../CloudHvVirtMemInfoPeiLib.inf              |  46 ++++
>  4 files changed, 319 insertions(+), 1 deletion(-)  create mode 100644
> ArmVirtPkg/Library/CloudHvVirtMemInfoLib/CloudHvVirtMemInfoLib.c
>  create mode 100644
> ArmVirtPkg/Library/CloudHvVirtMemInfoLib/CloudHvVirtMemInfoLib.h
>  create mode 100644
> ArmVirtPkg/Library/CloudHvVirtMemInfoLib/CloudHvVirtMemInfoPeiLib.inf
>
> --
> 2.17.1

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

      parent reply	other threads:[~2022-08-25  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  8:09 [PATCH v2 0/2] CloudHv/arm: Add specific mem info lib Jianyong Wu
2022-08-19  8:09 ` [PATCH v2 1/2] CloudHv/arm: add PeiMemInfoLib Jianyong Wu
2022-09-01 15:43   ` Sami Mujawar
2022-09-02  1:00     ` Jianyong Wu
2022-08-19  8:09 ` [PATCH 2/2] CloudHv/arm: switch PeiMemLib to its own Jianyong Wu
2022-09-01 15:43   ` Sami Mujawar
2022-08-25  7:29 ` Jianyong Wu [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-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=DB9PR08MB7511B5EDC2404D932581EE3DF4729@DB9PR08MB7511.eurprd08.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