Home
last modified time | relevance | path

Searched full:sv39 (Results 1 – 14 of 14) sorted by relevance

/linux/arch/riscv/boot/dts/andes/
H A Dqilai.dtsi27 mmu-type = "riscv,sv39";
52 mmu-type = "riscv,sv39";
78 mmu-type = "riscv,sv39";
104 mmu-type = "riscv,sv39";
/linux/arch/riscv/boot/dts/sifive/
H A Dfu540-c000.dtsi56 mmu-type = "riscv,sv39";
83 mmu-type = "riscv,sv39";
110 mmu-type = "riscv,sv39";
137 mmu-type = "riscv,sv39";
H A Dfu740-c000.dtsi57 mmu-type = "riscv,sv39";
84 mmu-type = "riscv,sv39";
111 mmu-type = "riscv,sv39";
138 mmu-type = "riscv,sv39";
/linux/arch/riscv/boot/dts/microchip/
H A Dmpfs.dtsi52 mmu-type = "riscv,sv39";
83 mmu-type = "riscv,sv39";
114 mmu-type = "riscv,sv39";
145 mmu-type = "riscv,sv39";
/linux/arch/riscv/boot/dts/sophgo/
H A Dcv180x-cpus.dtsi23 mmu-type = "riscv,sv39";
/linux/arch/riscv/boot/dts/allwinner/
H A Dsun20i-d1s.dtsi25 mmu-type = "riscv,sv39";
/linux/arch/riscv/boot/dts/renesas/
H A Dr9a07g043f.dtsi31 mmu-type = "riscv,sv39";
/linux/arch/riscv/mm/
H A Dkasan_init.c15 * Kasan shadow region must lie at a fixed address across sv39, sv48 and sv57
18 * For sv39, the region is aligned on PGDIR_SIZE so we only need to populate
/linux/Documentation/translations/zh_CN/arch/riscv/
H A Dvm-layout.rst35 RISC-V Linux Kernel SV39
/linux/arch/riscv/kernel/pi/
H A Dfdt_early.c217 if (!strcmp(mmu_type, "riscv,sv39")) in set_satp_mode_from_fdt()
/linux/Documentation/arch/riscv/
H A Dvm-layout.rst30 RISC-V Linux Kernel SV39
/linux/arch/riscv/kernel/
H A Dcpu.c300 sv_type = "sv39"; in print_mmu()
/linux/arch/riscv/boot/dts/canaan/
H A Dk210.dtsi20 * The K210 has an sv39 MMU following the privileged specification v1.9.
/linux/arch/riscv/include/asm/
H A Dpgtable.h1064 * - 0x4000000000 ( 256GB) for RV64 using SV39 mmu