Searched full:rv64 (Results 1 – 17 of 17) sorted by relevance
222 ("Zcf doesn't exist on RV64 as it contains no instructions") of227 ("Zcf doesn't exist on RV64 as it contains no instructions") of232 ("Zcf doesn't exist on RV64 as it contains no instructions") of237 ("Zcf doesn't exist on RV64 as it contains no instructions") of
46 The RISC-V kernel expects to be placed at a PMD boundary (2MB aligned for rv64
27 '-cpu', 'rv64',
1050 * In the RV64 Linux scheme, we give the user half of the virtual-address space1060 * Task size is 0x4000000000 for RV64 or 0x9fc00000 for RV32.1064 * - 0x4000000000 ( 256GB) for RV64 using SV39 mmu1065 * - 0x800000000000 ( 128TB) for RV64 using SV48 mmu1066 * - 0x100000000000000 ( 64PB) for RV64 using SV57 mmu
75 * rv64 PTE format:
387 * linear addresses are identical, but different for RV64. To ensure consistency, we in swsusp_arch_resume()388 * map it for both RV32 and RV64 kernels. in swsusp_arch_resume()
92 * RV64 and 4MB alignment for RV32 in elf_find_pbase()
269 seq_write(f, "rv64", 4); in print_isa()
37 * greater than BITS_PER_LONG (32 for RV32 and 64 for RV64). Ideally, SBI v0.2 in __sbi_v01_cpumask_to_hartmask()
74 * SZREG holds 4 for RV32 and 8 for RV64
132 * Align address to closest word (double word on rv64) that comes before in do_csum_with_alignment()
42 CROSS_FLAGS=(-M virt -cpu rv64,sscofpmf=true -smp 8)
88 Running vmtest on RV64
226 QEMU_MACHINE := -cpu rv64 -machine virt
7 * The code is based on the BPF JIT compiler for RV64 by Björn Töpel.
7 * The code is based on the BPF JIT compiler for RV64 by Björn Töpel and
1465 * Note that SPARSEMEM_VMEMMAP is only selected for rv64 and that we in vmemmap_populate()