Home
last modified time | relevance | path

Searched full:aarch64 (Results 1 – 25 of 138) sorted by relevance

123456

/Linux-v5.10/Documentation/arm64/
Dtagged-address-abi.rst2 AArch64 TAGGED ADDRESS ABI
11 ABI on AArch64 Linux.
16 On AArch64 the ``TCR_EL1.TBI0`` bit is set by default, allowing
22 2. AArch64 Tagged Address ABI
43 The AArch64 Tagged Address ABI has two stages of relaxation depending
61 - ``PR_SET_TAGGED_ADDR_CTRL``: enable or disable the AArch64 Tagged
67 - ``PR_TAGGED_ADDR_ENABLE``: enable AArch64 Tagged Address ABI.
72 - ``PR_GET_TAGGED_ADDR_CTRL``: get the status of the AArch64 Tagged
81 returns ``-EINVAL`` if the AArch64 Tagged Address ABI is globally
85 When the AArch64 Tagged Address ABI is enabled for a thread, the
[all …]
Dtagged-pointers.rst2 Tagged virtual addresses in AArch64 Linux
10 addresses in the AArch64 translation system and their potential uses
11 in AArch64 Linux.
23 an address tag of 0x00, unless the application enables the AArch64
39 userspace application did not enable the AArch64 Tagged Address ABI may
43 For these reasons, when the AArch64 Tagged Address ABI is disabled,
66 This behaviour is maintained when the AArch64 Tagged Address ABI is
Dmemory.rst2 Memory Layout on AArch64 Linux
7 This document describes the virtual memory layout used by the AArch64
11 AArch64 Linux uses either 3 levels or 4 levels of translation tables
29 AArch64 Linux memory layout with 4KB pages + 4 levels (48-bit)::
48 AArch64 Linux memory layout with 64KB pages + 3 levels (52-bit with HW support)::
Dbooting.rst2 Booting AArch64 Linux
10 is relevant to all public releases of the AArch64 Linux kernel.
12 The AArch64 exception model is made up of a number of exception levels
63 The AArch64 kernel does not currently provide a decompressor and
Damu.rst4 Activity Monitors Unit (AMU) extension in AArch64 Linux
12 support in AArch64 Linux.
Dpointer-authentication.rst2 Pointer authentication in AArch64 Linux
10 functionality in AArch64 Linux.
/Linux-v5.10/arch/arm64/kvm/
Dinject_fault.c37 * of the inherited bits have the same position in the AArch64/AArch32 SPSR_ELx
40 * For the SPSR_ELx layout for AArch64, see ARM DDI 0487E.a page C5-429.
43 * Here we manipulate the fields in order of the AArch64 SPSR_ELx layout, from
88 // PSTATE.UAO is set to zero upon any exception to AArch64 in enter_exception64()
98 // PSTATE.SS is set to zero upon any exception to AArch64 in enter_exception64()
101 // PSTATE.IL is set to zero upon any exception to AArch64 in enter_exception64()
104 // PSTATE.SSBS is set to SCTLR_ELx.DSSBS upon any exception to AArch64 in enter_exception64()
109 // PSTATE.BTYPE is set to zero upon any exception to AArch64 in enter_exception64()
141 * Here, the guest runs in AArch64 mode when in EL1. If we get in inject_abt64()
/Linux-v5.10/tools/testing/selftests/kvm/
DMakefile20 # for includes are in x86_64 sub-directory. s390x and aarch64 follow the
22 # s390x and aarch64.
29 UNAME_M := aarch64
38 LIBKVM_aarch64 = lib/aarch64/processor.c lib/aarch64/ucall.c
69 TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list
70 TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list-sve
D.gitignore2 /aarch64/get-reg-list
3 /aarch64/get-reg-list-sve
/Linux-v5.10/Documentation/translations/zh_CN/arm64/
Dmemory.txt27 Linux 在 AArch64 中的内存布局
32 本文档描述 AArch64 Linux 内核所使用的虚拟内存布局。此构架可以实现
35 AArch64 Linux 使用 3 级或 4 级转换表，其页大小配置为 4KB，对于用户和内核
45 AArch64 Linux 在页大小为 4KB，并使用 3 级转换表时的内存布局：
53 AArch64 Linux 在页大小为 4KB，并使用 4 级转换表时的内存布局：
61 AArch64 Linux 在页大小为 64KB，并使用 2 级转换表时的内存布局：
69 AArch64 Linux 在页大小为 64KB，并使用 3 级转换表时的内存布局：
Dtagged-pointers.txt25 Linux 在 AArch64 中带标记的虚拟地址
31 本文档简述了在 AArch64 地址转换系统中提供的带标记的虚拟地址及其在
32 AArch64 Linux 中的潜在用途。
Dbooting.txt27 启动 AArch64 Linux
34 AArch64 Linux 内核代码。
36 AArch64 异常模型由多个异常级（EL0 - EL3）组成，对于 EL0 和 EL1 异常级
81 AArch64 内核当前没有提供自解压代码，因此如果使用了压缩内核映像文件
Damu.rst8 AArch64 Linux 中扩展的活动监控单元
15 本文档简要描述了 AArch64 Linux 支持的活动监控单元的规范。
/Linux-v5.10/tools/testing/selftests/rcutorture/bin/
Dfunctions.sh126 qemu-system-aarch64)
151 elif echo $u | grep -q aarch64
153 echo qemu-system-aarch64
177 qemu-system-aarch64)
208 qemu-system-aarch64)
265 qemu-system-x86_64|qemu-system-i386|qemu-system-aarch64)
/Linux-v5.10/tools/build/feature/
DMakefile43 test-libunwind-aarch64.bin \
45 test-libunwind-debug-frame-aarch64.bin \
181 $(OUTPUT)test-libunwind-aarch64.bin:
182 $(BUILD) -lelf -lunwind-aarch64
187 $(OUTPUT)test-libunwind-debug-frame-aarch64.bin:
188 $(BUILD) -lelf -lunwind-aarch64
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Darm,vexpress-juno.yaml16 32 bit (Aarch32) and 64 bit (Aarch64) systems.
84 AArch64 CPU cores. It has 2 Cortex A57 CPU cores and 4 Cortex A53
117 - description: Arm Foundation model for Aarch64
119 - const: arm,foundation-aarch64
/Linux-v5.10/tools/perf/tests/shell/
Dtest_arm_coresight.sh43 …# touch 6512 1 branches:u: ffffb220824c strcmp+0xc (/lib/aarch64-linux-gn…
44 …# touch 6512 1 branches:u: ffffb22082e0 strcmp+0xa0 (/lib/aarch64-linux-g…
45 …# touch 6512 1 branches:u: ffffb2208320 strcmp+0xe0 (/lib/aarch64-linux-g…
/Linux-v5.10/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/
Dinstruction.json20 …unts writes to CONTEXTIDR in AArch32 state, and via the CONTEXTIDR_EL1 mnemonic in AArch64 state.",
31 …vent only counts writes to TTBR0/TTBR1 in AArch32 state and TTBR0_EL1/TTBR1_EL1 in AArch64 state.",
/Linux-v5.10/Documentation/trace/coresight/
Dcoresight-cpu-debug.rst43 - The driver supports a CPU running in either AArch64 or AArch32 mode. The
44 registers naming convention is a bit different between them, AArch64 uses
47 use AArch64 naming convention.
62 in AArch32 state, EDPCSR is not sampled; when the CPU operates in AArch64
/Linux-v5.10/tools/perf/
DMakefile.config74 LIBUNWIND_LIBS = -lunwind -lunwind-aarch64
120 LIBUNWIND_ARCHS = x86 x86_64 arm aarch64 debug-frame-arm debug-frame-aarch64
131 FEATURE_CHECK_LDFLAGS-libunwind-aarch64 = -lunwind -lunwind-aarch64
588 $(call feature_check,libunwind-aarch64)
589 ifeq ($(feature-libunwind-aarch64), 1)
592 LDFLAGS += -lunwind-aarch64
593 EXTLIBS_LIBUNWIND += -lunwind-aarch64
595 $(call feature_check,libunwind-debug-frame-aarch64)
596 ifneq ($(feature-libunwind-debug-frame-aarch64), 1)
597 msg := $(warning No debug_frame support found in libunwind-aarch64);
/Linux-v5.10/drivers/firmware/efi/
Dcper-arm.c26 "AArch64 general purpose registers",
27 "AArch64 EL1 context registers",
28 "AArch64 EL2 context registers",
29 "AArch64 EL3 context registers",
/Linux-v5.10/arch/arm64/include/asm/
Dkgdb.h3 * AArch64 KGDB support
44 * protocol for AArch64 was developed it depended on a statement in the
Dvermagic.h8 #define MODULE_ARCH_VERMAGIC "aarch64"
/Linux-v5.10/tools/testing/selftests/bpf/progs/
Dstrobemeta.h135 * tpidr_el0 for aarch64).
262 * For aarch64, this is pointed to by second GOT entry.
280 * (offset from fs:0 for x86-64 or tpidr_el0 for aarch64); in calc_location()
299 * For immediate executable mode (currently supported only for aarch64): in calc_location()
305 * - (for aarch64 only) second entry points to tls_index_t struct; in calc_location()
/Linux-v5.10/Documentation/kbuild/
Dllvm.rst41 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make CC=clang
47 clang --target=aarch64-linux-gnu foo.c

123456