The ARM architecture provides no reliable way to clean or invalidate
the entire data cache at runtime. The reason is that such maintenance
requires the use of set/way maintenance operations, which are suitable
only for the kind of maintenance that is carried out when the cache is
taken offline entirely.
So ASSERT () when any of the CacheMaintenanceLib whole data cache routines
are invoked rather than pretending we can do anything meaningful here.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel <ard.biesheu...@linaro.org>
---
ArmPkg/Library/ArmCacheMaintenanceLib/ArmCacheMaintenanceLib.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/ArmPkg/Library/ArmCacheMaintenanceLib/ArmCacheMaintenanceLib.c
b/ArmPkg/Library/ArmCacheMaintenanceLib/ArmCacheMaintenanceLib.c
index d4c16a607465..65ba8749e796 100644
--- a/ArmPkg/Library/ArmCacheMaintenanceLib/ArmCacheMaintenanceLib.c
+++ b/ArmPkg/Library/ArmCacheMaintenanceLib/ArmCacheMaintenanceLib.c
@@ -14,6 +14,7 @@
**/
#include <Base.h>
#include <Library/ArmLib.h>
+#include <Library/DebugLib.h>
#include <Library/PcdLib.h>
VOID
@@ -44,7 +45,6 @@ InvalidateInstructionCache (
VOID
)
{
- ArmCleanDataCache();
ArmInvalidateInstructionCache();
}
@@ -54,7 +54,7 @@ InvalidateDataCache (
VOID
)
{
- ArmInvalidateDataCache();
+ ASSERT (FALSE);
}
VOID *
@@ -75,7 +75,7 @@ WriteBackInvalidateDataCache (
VOID
)
{
- ArmCleanInvalidateDataCache();
+ ASSERT (FALSE);
}
VOID *
@@ -95,7 +95,7 @@ WriteBackDataCache (
VOID
)
{
- ArmCleanDataCache();
+ ASSERT (FALSE);
}
VOID *
--
1.9.1
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
