public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Jianyong Wu <Jianyong.Wu@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Justin He <Justin.He@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH 1/2] CloudHv/arm: add PeiMemInfoLib
Date: Thu, 18 Aug 2022 11:40:41 +0000	[thread overview]
Message-ID: <F08A9818-CF16-4727-8CE5-9732D909D7F1@arm.com> (raw)
In-Reply-To: <DB9PR08MB7511250441C490B79FF9C24AF46D9@DB9PR08MB7511.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]

Hi Jianyong,

Please find my response inline marked [SAMI].

Regards,

Sami Mujawar

From: Jianyong Wu <Jianyong.Wu@arm.com>
Date: Thursday, 18 August 2022 at 06:22
To: "devel@edk2.groups.io" <devel@edk2.groups.io>, Jianyong Wu <Jianyong.Wu@arm.com>, Sami Mujawar <Sami.Mujawar@arm.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>, Justin He <Justin.He@arm.com>, nd <nd@arm.com>
Subject: RE: [edk2-devel] [PATCH 1/2] CloudHv/arm: add PeiMemInfoLib

Hi Sami,

Thanks for review. All the comments are Ok for me. Just one inline reply:


+

+struct CloudHvMemNodeInfo CloudHvMemNode[CLOUDHV_MAX_MEM_NODE_NUM];

+

+RETURN_STATUS

+EFIAPI

+CloudHvVirtMemInfoPeiLibConstructor (

+  VOID

+  )

+{

+  VOID           *DeviceTreeBase;

+  EFI_RESOURCE_ATTRIBUTE_TYPE  ResourceAttributes;

+  INT32          Node, Prev;

+  UINT64         CurBase, MemBase;

+  UINT64         CurSize;

+  CONST CHAR8    *Type;

+  INT32          Len;

+  CONST UINT64   *RegProp;

+  RETURN_STATUS  PcdStatus;

+  UINT8          Index;

+

+  ZeroMem (CloudHvMemNode, sizeof(CloudHvMemNode[0]) * CLOUDHV_MAX_MEM_NODE_NUM);
[SAMI] Will sizeof (CloudHvMemNode) should be sufficient above? Also, can you run uncrustify on your patches, please?

[Jong] The local uncrustify test environment is not ready. But I think “sizeof” here is OK, as this struct contains only two u64 variables, thus no padding here. If sizeof is not preference here, is there any suggestion from you?
[SAMI] I think you could just use

+  ZeroMem (CloudHvMemNode, sizeof(CloudHvMemNode));

Also, let me know if you need any help to get uncrustify working locally. I will dig out the relevant information for you.

[/SAMI]


Thanks
Jianyong



[-- Attachment #2: Type: text/html, Size: 7324 bytes --]

  reply	other threads:[~2022-08-18 11:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  7:21 [PATCH 0/2] CloudHv/arm: Add specific mem info lib Jianyong Wu
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 [this message]
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=F08A9818-CF16-4727-8CE5-9732D909D7F1@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