From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
edk2-devel@ml01.01.org, leif.lindholm@linaro.org
Subject: Re: [PATCH] ArmVirtPkg: restrict mapping attributes of normal memory to EFI_MEMORY_WB
Date: Thu, 8 Sep 2016 09:54:27 +0200 [thread overview]
Message-ID: <5c99e1a8-f667-aaab-7214-df94816abd8e@redhat.com> (raw)
In-Reply-To: <1473321027-31091-1-git-send-email-ard.biesheuvel@linaro.org>
On 09/08/16 09:50, Ard Biesheuvel wrote:
> In general, on an ARM system, 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.
>
> Under KVM, the situation is even worse, since the host may not expect the
> guest to perform uncached accesses, and so writes to such an uncached
> region may get lost completely.
>
> Since the only safe mapping type under KVM is EFI_MEMORY_WB, remove all
> other memory type attributes.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> ArmVirtPkg/HighMemDxe/HighMemDxe.c | 3 +--
> ArmVirtPkg/Library/ArmVirtMemoryInitPeiLib/ArmVirtMemoryInitPeiLib.c | 3 ---
> 2 files changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/ArmVirtPkg/HighMemDxe/HighMemDxe.c b/ArmVirtPkg/HighMemDxe/HighMemDxe.c
> index 7fd7e8e9a539..4d56e6236b54 100644
> --- a/ArmVirtPkg/HighMemDxe/HighMemDxe.c
> +++ b/ArmVirtPkg/HighMemDxe/HighMemDxe.c
> @@ -78,8 +78,7 @@ InitializeHighMemDxe (
> Status = gDS->AddMemorySpace (
> EfiGcdMemoryTypeSystemMemory,
> CurBase, CurSize,
> - EFI_MEMORY_WB | EFI_MEMORY_WC |
> - EFI_MEMORY_WT | EFI_MEMORY_UC);
> + EFI_MEMORY_WB);
>
> if (EFI_ERROR (Status)) {
> DEBUG ((EFI_D_ERROR,
> diff --git a/ArmVirtPkg/Library/ArmVirtMemoryInitPeiLib/ArmVirtMemoryInitPeiLib.c b/ArmVirtPkg/Library/ArmVirtMemoryInitPeiLib/ArmVirtMemoryInitPeiLib.c
> index 251e5314e61d..6f3e54b7afcb 100644
> --- a/ArmVirtPkg/Library/ArmVirtMemoryInitPeiLib/ArmVirtMemoryInitPeiLib.c
> +++ b/ArmVirtPkg/Library/ArmVirtMemoryInitPeiLib/ArmVirtMemoryInitPeiLib.c
> @@ -68,9 +68,6 @@ MemoryPeim (
> ResourceAttributes = (
> EFI_RESOURCE_ATTRIBUTE_PRESENT |
> EFI_RESOURCE_ATTRIBUTE_INITIALIZED |
> - EFI_RESOURCE_ATTRIBUTE_UNCACHEABLE |
> - EFI_RESOURCE_ATTRIBUTE_WRITE_COMBINEABLE |
> - EFI_RESOURCE_ATTRIBUTE_WRITE_THROUGH_CACHEABLE |
> EFI_RESOURCE_ATTRIBUTE_WRITE_BACK_CACHEABLE |
> EFI_RESOURCE_ATTRIBUTE_TESTED
> );
>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Did you encounter any specific problem with these?
Thanks
Laszlo
next prev parent reply other threads:[~2016-09-08 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 7:50 [PATCH] ArmVirtPkg: restrict mapping attributes of normal memory to EFI_MEMORY_WB Ard Biesheuvel
2016-09-08 7:54 ` Laszlo Ersek [this message]
2016-09-08 7:57 ` Ard Biesheuvel
2016-09-08 9:38 ` 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=5c99e1a8-f667-aaab-7214-df94816abd8e@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