public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zeng, Star" <star.zeng@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, Ruiyu Ni <ruiyu.ni@intel.com>,
	edk2-devel@lists.01.org
Cc: star.zeng@intel.com
Subject: Re: [PATCH 3/3] MdeModulePkg/PciHostBridge: Add RESOURCE_VALID() to simplify code
Date: Tue, 25 Sep 2018 10:35:01 +0800	[thread overview]
Message-ID: <976f49ab-75e4-2009-ec78-e73a52212552@intel.com> (raw)
In-Reply-To: <12daedaa-952f-fc73-3ed5-62970f869ba9@redhat.com>

On 2018/9/21 19:12, Laszlo Ersek wrote:
> On 09/21/18 09:25, Ruiyu Ni wrote:
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
>> Cc: Star Zeng <star.zeng@intel.com>
>> ---
>>   .../Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c     | 26 ++++++++++------------
>>   1 file changed, 12 insertions(+), 14 deletions(-)
>>
>> diff --git a/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c b/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> index f6234b5d11..916709e276 100644
>> --- a/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> +++ b/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> @@ -21,6 +21,8 @@ extern EDKII_IOMMU_PROTOCOL        *mIoMmuProtocol;
>>   
>>   #define NO_MAPPING  (VOID *) (UINTN) -1
>>   
>> +#define RESOURCE_VALID(R) ((R).Base <= (R).Limit)
>> +
>>   //
>>   // Lookup table for increment values based on transfer widths
>>   //
>> @@ -122,25 +124,25 @@ CreateRootBridge (
>>     //
>>     // Make sure Mem and MemAbove4G apertures are valid
>>     //
>> -  if (Bridge->Mem.Base <= Bridge->Mem.Limit) {
>> +  if (RESOURCE_VALID (Bridge->Mem)) {
>>       ASSERT (Bridge->Mem.Limit < SIZE_4GB);
>>       if (Bridge->Mem.Limit >= SIZE_4GB) {
>>         return NULL;
>>       }
>>     }
>> -  if (Bridge->MemAbove4G.Base <= Bridge->MemAbove4G.Limit) {
>> +  if (RESOURCE_VALID (Bridge->MemAbove4G)) {
>>       ASSERT (Bridge->MemAbove4G.Base >= SIZE_4GB);
>>       if (Bridge->MemAbove4G.Base < SIZE_4GB) {
>>         return NULL;
>>       }
>>     }
>> -  if (Bridge->PMem.Base <= Bridge->PMem.Limit) {
>> +  if (RESOURCE_VALID (Bridge->PMem)) {
>>       ASSERT (Bridge->PMem.Limit < SIZE_4GB);
>>       if (Bridge->PMem.Limit >= SIZE_4GB) {
>>         return NULL;
>>       }
>>     }
>> -  if (Bridge->PMemAbove4G.Base <= Bridge->PMemAbove4G.Limit) {
>> +  if (RESOURCE_VALID (Bridge->PMemAbove4G)) {
>>       ASSERT (Bridge->PMemAbove4G.Base >= SIZE_4GB);
>>       if (Bridge->PMemAbove4G.Base < SIZE_4GB) {
>>         return NULL;
>> @@ -157,11 +159,9 @@ CreateRootBridge (
>>         // support separate windows for Non-prefetchable and Prefetchable
>>         // memory.
>>         //
>> -      ASSERT (Bridge->PMem.Base > Bridge->PMem.Limit);
>> -      ASSERT (Bridge->PMemAbove4G.Base > Bridge->PMemAbove4G.Limit);
>> -      if ((Bridge->PMem.Base <= Bridge->PMem.Limit) ||
>> -          (Bridge->PMemAbove4G.Base <= Bridge->PMemAbove4G.Limit)
>> -          ) {
>> +      ASSERT (!RESOURCE_VALID (Bridge->PMem));
>> +      ASSERT (!RESOURCE_VALID (Bridge->PMemAbove4G));
>> +      if (RESOURCE_VALID (Bridge->PMem) || RESOURCE_VALID (Bridge->PMemAbove4G)) {
>>           return NULL;
>>         }
>>       }
>> @@ -171,11 +171,9 @@ CreateRootBridge (
>>         // If this bit is not set, then the PCI Root Bridge does not support
>>         // 64 bit memory windows.
>>         //
>> -      ASSERT (Bridge->MemAbove4G.Base > Bridge->MemAbove4G.Limit);
>> -      ASSERT (Bridge->PMemAbove4G.Base > Bridge->PMemAbove4G.Limit);
>> -      if ((Bridge->MemAbove4G.Base <= Bridge->MemAbove4G.Limit) ||
>> -          (Bridge->PMemAbove4G.Base <= Bridge->PMemAbove4G.Limit)
>> -          ) {
>> +      ASSERT (!RESOURCE_VALID (Bridge->MemAbove4G));
>> +      ASSERT (!RESOURCE_VALID (Bridge->PMemAbove4G));
>> +      if (RESOURCE_VALID (Bridge->MemAbove4G) || RESOURCE_VALID (Bridge->PMemAbove4G)) {
>>           return NULL;
>>         }
>>       }
>>
> 
> Two superficial comments:
> 
> - edk2 prefers long parameter names, so I suggest replacing "R" in the
> macro definition with "Resource"
> 
> - taking the parameter as a pointer is frequently considered more flexible.
> 
> #define RESOURCE_VALID(Resource) ((Resource)->Base <= (Resource)->Limit)
> ....
> if (RESOURCE_VALID (&Bridge->Mem)) {
> ....
> 
> Up to you -- if you like these, feel free to update the patch before
> pushing it (from my side anyway; you do need MdeModulePkg maintainer
> review as well).

I have no strong preference here. Let Ray to make the choice.
I have another very small comment.
Is it better to add "#define RESOURCE_VALID(R) ((R).Base <= (R).Limit)" 
in PciRootBridge.h?
Also move "#define NO_MAPPING  (VOID *) (UINTN) -1" into PciRootBridge.h?
And also move "extern EDKII_IOMMU_PROTOCOL        *mIoMmuProtocol;" into 
PciHostBridge.h?

Thanks,
Star

> 
> With or without changes:
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> 
> Thanks
> Laszlo
> 



  parent reply	other threads:[~2018-09-25  2:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  7:25 [PATCH 0/3] Fix a bug that prevents PMEM access Ruiyu Ni
2018-09-21  7:25 ` [PATCH 1/3] MdeModulePkg/PciHostBridge: Enhance boundary check in Io/Mem.Read/Write Ruiyu Ni
2018-09-21 10:53   ` Laszlo Ersek
2018-09-24 13:18   ` Kirkendall, Garrett
2018-09-25  2:14   ` Zeng, Star
2018-09-25  2:43     ` Ni, Ruiyu
2018-09-25  3:02       ` Zeng, Star
2018-09-21  7:25 ` [PATCH 2/3] MdeModulePkg/PciHostBridge: Fix a bug that prevents PMEM access Ruiyu Ni
2018-09-21 11:06   ` Laszlo Ersek
2018-09-25  2:11     ` Ni, Ruiyu
2018-09-24 13:19   ` Kirkendall, Garrett
2018-09-25  2:15   ` Zeng, Star
2018-09-21  7:25 ` [PATCH 3/3] MdeModulePkg/PciHostBridge: Add RESOURCE_VALID() to simplify code Ruiyu Ni
2018-09-21 11:12   ` Laszlo Ersek
2018-09-25  2:25     ` Ni, Ruiyu
2018-09-25  2:35     ` Zeng, Star [this message]
2018-09-25  2:47       ` Ni, Ruiyu
2018-09-25  3:13         ` Zeng, Star
2018-09-25  5:03           ` Ni, Ruiyu
2018-09-24 13:20   ` Kirkendall, Garrett

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=976f49ab-75e4-2009-ec78-e73a52212552@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