diff options
author | Sergey Bugaev <bugaevc@gmail.com> | 2024-04-15 12:01:41 +0300 |
---|---|---|
committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2024-04-16 09:36:19 +0900 |
commit | b792f1eb08e34db89ac200a86ea7e6859a6b0668 (patch) | |
tree | b806ae842486755e9cbc6e11275060ef133177bd /aarch64 | |
parent | 782b800f2aecfe39ce5d9cdd8cc7b4c7f36ea398 (diff) | |
download | gnumach-b792f1eb08e34db89ac200a86ea7e6859a6b0668.tar.gz gnumach-b792f1eb08e34db89ac200a86ea7e6859a6b0668.tar.bz2 gnumach-b792f1eb08e34db89ac200a86ea7e6859a6b0668.zip |
Add CPU_TYPE_ARM64
This is distinct from CPU_TYPE_ARM, since we're going to exclusively use
AArch64 / A64, which CPU_TYPE_ARM was never meant to support, and to
match EM_AARCH64, which is also separate from EM_ARM. CPU_TYPE_X86_64
was similarly made distinct from CPU_TYPE_I386.
This is named CPU_TYPE_ARM64 rather than CPU_TYPE_AARCH64, since AArch64
is an "execution state" (analogous to long mode on x86_64) rather than a
CPU type. "ARM64" here is not a name of the architecture, but simply
means an ARM CPU that is capable of (and for our case, will only really
be) running in the 64-bit mode (AArch64).
There are no subtypes defined, and none are expected to be defined in
the future. Support for individual features/extensions should be
discovered by other means, i.e. the aarch64_get_hwcaps() RPC.
Message-ID: <20240415090149.38358-2-bugaevc@gmail.com>
Diffstat (limited to 'aarch64')
0 files changed, 0 insertions, 0 deletions