From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io, pete@akeo.ie,
Andrei Warkentin <awarkentin@vmware.com>
Cc: "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"leif@nuviainc.com" <leif@nuviainc.com>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH 1/2] Platform/RaspberryPi/Drivers/ConfigDxe: fix bug in 3GB RAM logic
Date: Thu, 5 Mar 2020 12:58:53 +0100 [thread overview]
Message-ID: <fb45d9aa-420d-7a15-e2b5-d6a4ee069ca1@redhat.com> (raw)
In-Reply-To: <3849ba68-378d-88ab-dd70-9ab19bf35853@akeo.ie>
On 3/5/20 12:38 AM, Pete Batard wrote:
> On 2020.03.04 22:31, Andrei Warkentin wrote:
>> The original change*** used positive logic (PcdPi4GBEnabled), while the
>> upstreamed change uses negative logic (PcdRamLimitTo3GB), which
>> requires an additional condition, or it blows up on 1GiB and 2GiB boards.
>
> Good catch!
>
>> Tested on 2GB and 4GB boards (with limiting and without)
>>
>> *** https://github.com/pftf/edk2-platforms/\
>> commit/968451beb7c9302517098abf72f7e42b57a0e024
>>
>> Signed-off-by: Andrei Warkentin <awarkentin@vmware.com>
>> ---
>> Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> index ccac8daa..5fca3c7a 100644
>> --- a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> +++ b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
>> @@ -288,7 +288,8 @@ ApplyVariables (
>> DEBUG ((DEBUG_INFO, "Current CPU speed is %uHz\n", Rate));
>> }
>> - if (mModelFamily >= 4 && PcdGet32 (PcdRamLimitTo3GB) == 0) {
>> + if (mModelFamily >= 4 && PcdGet32 (PcdRamMoreThan3GB) &&
>
> Just a super minor nitpick, but if we want to be consistent with the
> next line, where we use the comparison to the integer value as the
> boolean, instead of using the result of the PcdGet operation itself,
> then the condition above should be:
>
> if (mModelFamily >= 4 && PcdGet32 (PcdRamMoreThan3GB) != 0 &&
Yes please. Can the maintainer amend that change? It can be quicker to
simply repost. With the change:
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
>
> Since it doesn't matter either way, I'm 100% fine with the patch as it
> stands. It's just that I remember trying to go for an explicit integer
> comparison for code clarity, on account that we went for integer PCDs
> rather than boolean ones...
>
>> + PcdGet32 (PcdRamLimitTo3GB) == 0) {
>> /*
>> * Similar to how we compute the > 3 GB RAM segment's size in
>> PlatformLib/
>> * RaspberryPiMem.c, with some overlap protection for the
>> Bcm2xxx register
>>
>
> Reviewed-by: Pete Batard <pete@akeo.ie>
>
>
>
>
next prev parent reply other threads:[~2020-03-05 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 22:31 [edk2-platforms][PATCH 0/2] RPi4 fixes to 3GB RAM limit logic Andrei Warkentin
2020-03-04 22:31 ` [edk2-platforms][PATCH 1/2] Platform/RaspberryPi/Drivers/ConfigDxe: fix bug in 3GB RAM logic Andrei Warkentin
2020-03-04 23:38 ` Pete Batard
2020-03-05 11:58 ` Philippe Mathieu-Daudé [this message]
2020-03-04 22:31 ` [edk2-platforms][PATCH 2/2] Platform/RaspberryPi/Drivers/PlatformSmbiosDxe: improve UX with 3GB limit Andrei Warkentin
2020-03-04 23:38 ` Pete Batard
2020-03-05 13:52 ` [edk2-platforms][PATCH 0/2] RPi4 fixes to 3GB RAM limit logic Ard Biesheuvel
2020-03-05 13:55 ` Ard Biesheuvel
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=fb45d9aa-420d-7a15-e2b5-d6a4ee069ca1@redhat.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