summaryrefslogtreecommitdiff
path: root/src/cpu/x86/cache
diff options
context:
space:
mode:
authorArthur Heymans <arthur@aheymans.xyz>2019-11-25 12:20:01 +0100
committerLean Sheng Tan <sheng.tan@9elements.com>2023-03-13 13:42:32 +0000
commit3134a8152590f6d93232f6e56ab08fd87ebe1a0d (patch)
tree8a7569aa1f9f204e36cc7571bd2ed71eca714b24 /src/cpu/x86/cache
parent4bad919ce47fae7187dfc8ed0c0186a78fd10597 (diff)
cpu/x86/cache: CLFLUSH programs to memory before running
When cbmem is initialized in romstage and postcar placed in the stage cache + cbmem where it is run, the assumption is made that these are all in UC memory such that calling INVD in postcar is OK. For performance reasons (e.g. postcar decompression) it is desirable to cache cbmem and the stage cache during romstage. Another reason is that AGESA sets up MTRR during romstage to cache all dram, which is currently worked around by using additional MTRR's to make that UC. TESTED on asus/p5ql-em, up/squared on both regular and S3 resume bootpath. Sometimes there are minimal performance improvements when cbmem is cached (few ms). Change-Id: I7ff2a57aee620908b71829457ea0f5a0c410ec5b Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37196 Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com> Reviewed-by: Kapil Porwal <kapilporwal@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/cpu/x86/cache')
-rw-r--r--src/cpu/x86/cache/Makefile.inc2
-rw-r--r--src/cpu/x86/cache/cache.c58
2 files changed, 60 insertions, 0 deletions
diff --git a/src/cpu/x86/cache/Makefile.inc b/src/cpu/x86/cache/Makefile.inc
new file mode 100644
index 0000000000..759488ec7e
--- /dev/null
+++ b/src/cpu/x86/cache/Makefile.inc
@@ -0,0 +1,2 @@
+romstage-y += cache.c
+ramstage-y += cache.c
diff --git a/src/cpu/x86/cache/cache.c b/src/cpu/x86/cache/cache.c
new file mode 100644
index 0000000000..d02d6d4427
--- /dev/null
+++ b/src/cpu/x86/cache/cache.c
@@ -0,0 +1,58 @@
+/* SPDX-License-Identifier: GPL-2.0-only */
+
+#include <arch/cpu.h>
+#include <cbmem.h>
+#include <console/console.h>
+#include <cpu/x86/cache.h>
+#include <program_loading.h>
+#include <types.h>
+
+bool clflush_supported(void)
+{
+ return (cpuid_edx(1) >> CPUID_FEATURE_CLFLUSH_BIT) & 1;
+}
+
+static void clflush_region(const uintptr_t start, const size_t size)
+{
+ uintptr_t addr;
+ const size_t cl_size = ((cpuid_ebx(1) >> 8) & 0xff) * 8;
+
+ if (!clflush_supported()) {
+ printk(BIOS_DEBUG, "Not flushing cache to RAM, CLFLUSH not supported\n");
+ return;
+ }
+
+ printk(BIOS_SPEW, "CLFLUSH [0x%lx, 0x%lx]\n", start, start + size);
+
+ for (addr = ALIGN_DOWN(start, cl_size); addr < start + size; addr += cl_size)
+ clflush((void *)addr);
+}
+
+/*
+ * For each segment of a program loaded this function is called
+ * to invalidate caches for the addresses of the loaded segment
+ */
+void arch_segment_loaded(uintptr_t start, size_t size, int flags)
+{
+ /* INVD is only called in postcar stage so we only need
+ to make sure that our code hits dram during romstage. */
+ if (!ENV_CACHE_AS_RAM)
+ return;
+ if (!ENV_ROMSTAGE)
+ return;
+ if (!CONFIG(POSTCAR_STAGE))
+ return;
+ if (!CONFIG(X86_CLFLUSH_CAR))
+ return;
+ if (flags != SEG_FINAL)
+ return;
+
+ /*
+ * The assumption is made here that DRAM is only ready after cbmem
+ * is initialized, to avoid flushing when loading earlier things (e.g. FSP, ...)
+ */
+ if (!cbmem_online())
+ return;
+
+ clflush_region(start, size);
+}