From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Leif Lindholm <leif@nuviainc.com>
Subject: Re: [edk2-devel] [PATCH 1/1] ArmPlatformPkg/PrePeiCore: replace set/way cache ops with by-VA ones
Date: Wed, 4 Mar 2020 18:46:51 +0100 [thread overview]
Message-ID: <CAKv+Gu_5+MLdsbggU5k-9cHm+ZcbPcPDBsE_EDDaBRG0gEfu=A@mail.gmail.com> (raw)
In-Reply-To: <d5ffe25d-e5f6-9172-989d-c9ed2de10835@redhat.com>
On Fri, 21 Feb 2020 at 16:54, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 02/21/20 12:07, Ard Biesheuvel wrote:
> > Cache maintenance operations by set/way are only intended to be used
> > in the context of on/offlining a core, while it has been taken out of
> > the coherency domain. Any use intended to ensure that the contents of
> > the cache have made it to main memory is unreliable, since cacheline
> > migration and non-architected system caches may cause these contents
> > to linger elsewhere, without being visible in main memory once the
> > MMU and caches are disabled.
> >
> > In KVM on Linux, there are horrid hacks in place to ensure that such
> > set/way operations are trapped, and replaced with a single by-VA
> > clean/invalidate of the entire guest VA space once the MMU state
> > changes, which can be costly, and is unnecessary if we manage the
> > caches a bit more carefully, and perform maintenance by virtual
> > address only.
> >
> > So let's get rid of the call to ArmInvalidateDataCache () in the
> > PrePeiCore startup code, and instead, invalidate the temporary RAM
> > region by virtual address, which is the only memory region we will
> > be touching with the caches and MMU both disabled and enabled.
> > (This will lead to data corruption if data written with the MMU off
> > is shadowed by clean, stale cachelines that stick around when the
> > MMU is enabled again.)
> >
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> > ---
> > Tested on bare metal (SynQuacer 32-bit) and KVM (mach-virt 64-bit)
> >
> > ArmPlatformPkg/PrePeiCore/PrePeiCore.c | 6 ++++--
> > ArmPlatformPkg/PrePeiCore/PrePeiCoreMPCore.inf | 1 +
> > ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf | 1 +
> > 3 files changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/ArmPlatformPkg/PrePeiCore/PrePeiCore.c b/ArmPlatformPkg/PrePeiCore/PrePeiCore.c
> > index 4911f67577a2..a7a61fe9ddb5 100644
> > --- a/ArmPlatformPkg/PrePeiCore/PrePeiCore.c
> > +++ b/ArmPlatformPkg/PrePeiCore/PrePeiCore.c
> > @@ -8,6 +8,7 @@
> > **/
> >
> > #include <Library/BaseLib.h>
> > +#include <Library/CacheMaintenanceLib.h>
> > #include <Library/DebugAgentLib.h>
> > #include <Library/ArmLib.h>
> >
> > @@ -59,13 +60,14 @@ CEntryPoint (
> > {
> > // Data Cache enabled on Primary core when MMU is enabled.
> > ArmDisableDataCache ();
> > - // Invalidate Data cache
> > - ArmInvalidateDataCache ();
> > // Invalidate instruction cache
> > ArmInvalidateInstructionCache ();
> > // Enable Instruction Caches on all cores.
> > ArmEnableInstructionCache ();
> >
> > + InvalidateDataCacheRange ((VOID *)(UINTN)PcdGet64 (PcdCPUCoresStackBase),
> > + PcdGet32 (PcdCPUCorePrimaryStackSize));
> > +
> > //
> > // Note: Doesn't have to Enable CPU interface in non-secure world,
> > // as Non-secure interface is already enabled in Secure world.
> > diff --git a/ArmPlatformPkg/PrePeiCore/PrePeiCoreMPCore.inf b/ArmPlatformPkg/PrePeiCore/PrePeiCoreMPCore.inf
> > index f2ac45d171bc..9d90d46dcfc5 100644
> > --- a/ArmPlatformPkg/PrePeiCore/PrePeiCoreMPCore.inf
> > +++ b/ArmPlatformPkg/PrePeiCore/PrePeiCoreMPCore.inf
> > @@ -44,6 +44,7 @@ [Packages]
> > [LibraryClasses]
> > ArmLib
> > ArmPlatformLib
> > + CacheMaintenanceLib
> > BaseLib
> > DebugLib
> > DebugAgentLib
> > diff --git a/ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf b/ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf
> > index 84c319c3679b..0749a6d575cf 100644
> > --- a/ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf
> > +++ b/ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf
> > @@ -44,6 +44,7 @@ [Packages]
> > [LibraryClasses]
> > ArmLib
> > ArmPlatformLib
> > + CacheMaintenanceLib
> > BaseLib
> > DebugLib
> > DebugAgentLib
> >
>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
>
Pushed as 6c9a3d4233d78a04db5f25aeed254396740f4cae
Thanks all
prev parent reply other threads:[~2020-03-04 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:07 [PATCH 1/1] ArmPlatformPkg/PrePeiCore: replace set/way cache ops with by-VA ones Ard Biesheuvel
2020-02-21 11:47 ` [edk2-devel] " Leif Lindholm
2020-02-21 15:54 ` Laszlo Ersek
2020-03-04 17:46 ` Ard Biesheuvel [this message]
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_5+MLdsbggU5k-9cHm+ZcbPcPDBsE_EDDaBRG0gEfu=A@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