From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ArmPlatformPkg: remove EFI_MEMORY_UC attribute from normal memory
Date: Thu, 8 Sep 2016 10:39:18 +0100 [thread overview]
Message-ID: <CAKv+Gu-QDJZUqFwTAB_BVkyNxL95mtVY2L46SBfOQeXiKxtP0w@mail.gmail.com> (raw)
In-Reply-To: <20160908092153.GH16080@bivouac.eciton.net>
On 8 September 2016 at 10:21, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Thu, Sep 08, 2016 at 09:13:38AM +0100, Ard Biesheuvel wrote:
>> On ARM systems, mapping normal memory as device memory may have unintended
>> side effects, given that unaligned accesses or loads and stores with special
>> semantics (e.g., load/store exclusive) may fault or may not work as expected.
>> Similarly, DC ZVA instructions are only supported on normal memory, not
>> device memory.
>
> I think this is the right thing to do; Arguably, on the modern ARM
> architectures, UNCACHEABLE and WRITE_COMBINEABLE are mutually
> exclusive. I'll discuss with Charles whether we should codify this in
> the UEFI specification.
>
>> So remove the EFI_MEMORY_UC attribute that we set by default on system RAM.
>> If any region requires this attribute, it is up to the driver to set this
>> attribute, and to ensure that no offending operations are performed on it.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
>
Pushed, thanks.
I will follow up with similar patches for OpenPlatformPkg
next prev parent reply other threads:[~2016-09-08 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 8:13 [PATCH] ArmPlatformPkg: remove EFI_MEMORY_UC attribute from normal memory Ard Biesheuvel
2016-09-08 9:21 ` Leif Lindholm
2016-09-08 9:39 ` Ard Biesheuvel [this message]
2016-09-08 17:37 ` Cohen, Eugene
2016-09-08 20:54 ` Leif Lindholm
2016-09-08 17:33 ` Cohen, Eugene
2016-09-08 17:49 ` 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=CAKv+Gu-QDJZUqFwTAB_BVkyNxL95mtVY2L46SBfOQeXiKxtP0w@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