From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Ryan Harkin <ryan.harkin@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Jeremy Linton <jeremy.linton@arm.com>
Subject: Re: [PATCH 2/2] ArmPlatformPkg/PL111LcdArmVExpressLib: use write-combine mapping for VRAM
Date: Thu, 6 Apr 2017 12:32:59 +0100 [thread overview]
Message-ID: <CAKv+Gu_mG4xdk7Vi9cmb-3HufEutTrZ4KoVjGqHDngb7PoUHbA@mail.gmail.com> (raw)
In-Reply-To: <CAD0U-h+Sry6Sm365dpQuwJ76kMMSxehP1tVPBOCqaXA=xUZgyA@mail.gmail.com>
On 6 April 2017 at 12:14, Ryan Harkin <ryan.harkin@linaro.org> wrote:
> On 5 April 2017 at 21:38, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> Replace the uncached memory mapping of the framebuffer with a write-
>> combining one. This improves performance, and avoids issues with
>> unaligned accesses and DC ZVA instructions performed by the accelerated
>> memcpy/memset routines.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Well, ... PL111 isn't usually enabled for me. And if I enable it,
> neither Foundation nor AEMv8 models boot with or without this patch.
>
> So it's no worse than before....
>
Not even foundation model? That is strange ...
>
>> ---
>> ArmPlatformPkg/ArmVExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/ArmPlatformPkg/ArmVExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c b/ArmPlatformPkg/ArmVExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c
>> index 2000c9bdf436..d18d6b3e1665 100644
>> --- a/ArmPlatformPkg/ArmVExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c
>> +++ b/ArmPlatformPkg/ArmVExpressPkg/Library/PL111LcdArmVExpressLib/PL111LcdArmVExpress.c
>> @@ -192,7 +192,7 @@ LcdPlatformGetVram (
>> ASSERT_EFI_ERROR(Status);
>>
>> // Mark the VRAM as un-cachable. The VRAM is inside the DRAM, which is cachable.
>> - Status = Cpu->SetMemoryAttributes(Cpu, *VramBaseAddress, *VramSize, EFI_MEMORY_UC);
>> + Status = Cpu->SetMemoryAttributes(Cpu, *VramBaseAddress, *VramSize, EFI_MEMORY_WC);
>> ASSERT_EFI_ERROR(Status);
>> if (EFI_ERROR(Status)) {
>> gBS->FreePool(VramBaseAddress);
>> --
>> 2.7.4
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-04-06 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 20:38 [PATCH 1/2] ArmPlatformPkg/HdLcdArmVExpressLib: use write-combine mapping for VRAM Ard Biesheuvel
2017-04-05 20:38 ` [PATCH 2/2] ArmPlatformPkg/PL111LcdArmVExpressLib: " Ard Biesheuvel
2017-04-06 11:14 ` Ryan Harkin
2017-04-06 11:32 ` Ard Biesheuvel [this message]
2017-04-06 11:43 ` Ryan Harkin
2017-04-06 9:37 ` [PATCH 1/2] ArmPlatformPkg/HdLcdArmVExpressLib: " Leif Lindholm
2017-04-06 10:40 ` Ard Biesheuvel
2017-04-06 11:15 ` Ryan Harkin
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=CAKv+Gu_mG4xdk7Vi9cmb-3HufEutTrZ4KoVjGqHDngb7PoUHbA@mail.gmail.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