arm64: hibernate: abstract ttrb0 setup function

Currently, only hibernate sets custom ttbr0 with safe idmaped function.
Kexec, is also going to be using this functionality when relocation code
is going to be idmapped.

Move the setup sequence to a dedicated cpu_install_ttbr0() for custom
ttbr0.

Suggested-by: James Morse <james.morse@arm.com>
Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Link: https://lore.kernel.org/r/20210930143113.1502553-4-pasha.tatashin@soleen.com
Signed-off-by: Will Deacon <will@kernel.org>

diff --git a/arch/arm64/include/asm/mmu_context.h b/arch/arm64/include/asm/mmu_context.h
index f4ba93d4ffebe9ddc763056ff4a7664c0be64e9a..6770667b34a31dcf983b371f26e9a9f86eb52a2e 100644 (file)
--- a/arch/arm64/include/asm/mmu_context.h
+++ b/arch/arm64/include/asm/mmu_context.h
@@ -115,6 +115,30 @@ static inline void cpu_install_idmap(void)
        cpu_switch_mm(lm_alias(idmap_pg_dir), &init_mm);
 }
 
+/*
+ * Load our new page tables. A strict BBM approach requires that we ensure that
+ * TLBs are free of any entries that may overlap with the global mappings we are
+ * about to install.
+ *
+ * For a real hibernate/resume/kexec cycle TTBR0 currently points to a zero
+ * page, but TLBs may contain stale ASID-tagged entries (e.g. for EFI runtime
+ * services), while for a userspace-driven test_resume cycle it points to
+ * userspace page tables (and we must point it at a zero page ourselves).
+ *
+ * We change T0SZ as part of installing the idmap. This is undone by
+ * cpu_uninstall_idmap() in __cpu_suspend_exit().
+ */
+static inline void cpu_install_ttbr0(phys_addr_t ttbr0, unsigned long t0sz)
+{
+       cpu_set_reserved_ttbr0();
+       local_flush_tlb_all();
+       __cpu_set_tcr_t0sz(t0sz);
+
+       /* avoid cpu_switch_mm() and its SW-PAN and CNP interactions */
+       write_sysreg(ttbr0, ttbr0_el1);
+       isb();
+}
+
 /*
  * Atomically replaces the active TTBR1_EL1 PGD with a new VA-compatible PGD,
  * avoiding the possibility of conflicting TLB entries being allocated.

diff --git a/arch/arm64/kernel/hibernate.c b/arch/arm64/kernel/hibernate.c
index b96ef9060e4cdd0cbfafe0a3fc08f18e3e4c27f1..2758f75d6809aaa01af0b3d6ba6a9e9c58b615f0 100644 (file)
--- a/arch/arm64/kernel/hibernate.c
+++ b/arch/arm64/kernel/hibernate.c
@@ -212,26 +212,7 @@ static int create_safe_exec_page(void *src_start, size_t length,
        if (rc)
                return rc;
 
-       /*
-        * Load our new page tables. A strict BBM approach requires that we
-        * ensure that TLBs are free of any entries that may overlap with the
-        * global mappings we are about to install.
-        *
-        * For a real hibernate/resume cycle TTBR0 currently points to a zero
-        * page, but TLBs may contain stale ASID-tagged entries (e.g. for EFI
-        * runtime services), while for a userspace-driven test_resume cycle it
-        * points to userspace page tables (and we must point it at a zero page
-        * ourselves).
-        *
-        * We change T0SZ as part of installing the idmap. This is undone by
-        * cpu_uninstall_idmap() in __cpu_suspend_exit().
-        */
-       cpu_set_reserved_ttbr0();
-       local_flush_tlb_all();
-       __cpu_set_tcr_t0sz(t0sz);
-       write_sysreg(trans_ttbr0, ttbr0_el1);
-       isb();
-
+       cpu_install_ttbr0(trans_ttbr0, t0sz);
        *phys_dst_addr = virt_to_phys(page);
 
        return 0;