a2ab46adbc
On ARMv7 and up, doing cache maintenance by set/way is only permitted in the context of on/offlining a core, and any other uses should be avoided. Add ASSERT()s in the right place to ensure that any uses with the MMU enabled are caught in DEBUG builds. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Reviewed-by: Leif Lindholm <leif@nuviainc.com>
74 lines
1.3 KiB
C
74 lines
1.3 KiB
C
/** @file
|
|
|
|
Copyright (c) 2008 - 2009, Apple Inc. All rights reserved.<BR>
|
|
Portions copyright (c) 2011 - 2014, ARM Ltd. All rights reserved.<BR>
|
|
|
|
SPDX-License-Identifier: BSD-2-Clause-Patent
|
|
|
|
**/
|
|
|
|
#include <Base.h>
|
|
|
|
#include <Library/ArmLib.h>
|
|
#include <Library/DebugLib.h>
|
|
|
|
#include <Chipset/AArch64.h>
|
|
|
|
#include "AArch64Lib.h"
|
|
#include "ArmLibPrivate.h"
|
|
|
|
VOID
|
|
AArch64DataCacheOperation (
|
|
IN AARCH64_CACHE_OPERATION DataCacheOperation
|
|
)
|
|
{
|
|
UINTN SavedInterruptState;
|
|
|
|
SavedInterruptState = ArmGetInterruptState ();
|
|
ArmDisableInterrupts();
|
|
|
|
AArch64AllDataCachesOperation (DataCacheOperation);
|
|
|
|
ArmDataSynchronizationBarrier ();
|
|
|
|
if (SavedInterruptState) {
|
|
ArmEnableInterrupts ();
|
|
}
|
|
}
|
|
|
|
VOID
|
|
EFIAPI
|
|
ArmInvalidateDataCache (
|
|
VOID
|
|
)
|
|
{
|
|
ASSERT (!ArmMmuEnabled ());
|
|
|
|
ArmDataSynchronizationBarrier ();
|
|
AArch64DataCacheOperation (ArmInvalidateDataCacheEntryBySetWay);
|
|
}
|
|
|
|
VOID
|
|
EFIAPI
|
|
ArmCleanInvalidateDataCache (
|
|
VOID
|
|
)
|
|
{
|
|
ASSERT (!ArmMmuEnabled ());
|
|
|
|
ArmDataSynchronizationBarrier ();
|
|
AArch64DataCacheOperation (ArmCleanInvalidateDataCacheEntryBySetWay);
|
|
}
|
|
|
|
VOID
|
|
EFIAPI
|
|
ArmCleanDataCache (
|
|
VOID
|
|
)
|
|
{
|
|
ASSERT (!ArmMmuEnabled ());
|
|
|
|
ArmDataSynchronizationBarrier ();
|
|
AArch64DataCacheOperation (ArmCleanDataCacheEntryBySetWay);
|
|
}
|