TrustedFirmware Git Browser
Code Review Sign In
review.trustedfirmware.org / hafnium / hafnium.git / 402b1fef34f7b6737f690a96d7484cced63e33cf
commit402b1fef34f7b6737f690a96d7484cced63e33cf[log] [tgz]
authorKarl Meakin <karl.meakin@arm.com>Thu Mar 20 14:52:55 2025 +0000
committerJ-Alves <joao.alves@arm.com>Mon Jun 16 10:48:28 2025 +0100
tree9e49b2b1fc829543bc1fe851d7b4c91763ff584b
parent34cd6a7cf0b9a79243511367630ba206b0fcb2f4 [diff]
refactor: warn against implicit fallthrough

Enable the `-Wimplicit-fallthrough` warning, which will warn if `case`
statements in a `switch` block fall through to the next `case`.
Intentional fallthrough can be signalled with the `[[fallthrough]]`
attribute which was added in C23.

Change-Id: I421cacadafba6457847c3a067483c97fdd9896cf
Signed-off-by: Karl Meakin <karl.meakin@arm.com>
8 files changed
tree: 9e49b2b1fc829543bc1fe851d7b4c91763ff584b
  1. .vscode/
  2. build/
  3. docs/
  4. inc/
  5. kokoro/
  6. project/
  7. src/
  8. test/
  9. third_party/
  10. vmlib/
  11. prebuilts
  12. .clang-format
  13. .clang-tidy
  14. .gitignore
  15. .gitmodules
  16. .gn
  17. .readthedocs.yaml
  18. AUTHORS
  19. BUILD.gn
  20. CONTRIBUTING.md
  21. dco.txt
  22. LICENSE
  23. Makefile
  24. navbar.md
  25. pyproject.toml
  26. README.md
README.md

Hafnium

Hafnium is the Secure Partition Manager(SPM) reference implementation, following the Arm's Firmware Framework specification.

It leverages Arm's virtualization extensions in the secure world of Arm's A class of devices (feature introduced with Armv8.4 FEAT_SEL2) to allow multiple Trusted OSes or Applications to run concurrently, inside the Trusted Execution Environment, each running as a Secure Partition (SP). Its main goal is to control the system access given to Trusted OSes, and serve as a mediator to the rest of the system.

For example, it limits the memory use, and handles all system calls from Trusted OS. Thus the SPM can enforce spacial isolation, and enforce some level of access control, protecting other critical system resources such as: the secure monitor, the normal world software stack, the SPM itself and other SPs/Trusted Applications. Other important features are: secure interrupt handling, device assignment, inter-partition communication and with the Normal World Software stack, also known as Rich Execution Environment (REE).

The following diagram shows an overview of a typical aarch64-based system, and where Hafnium fits:

Hafnium Architecture

Get in touch and keep up-to-date at:

See feature requests and bugs through github.

Documentation

To find more about Hafnium, view the full documentation. It includes valuable resources such as: Getting Started guide, Threat Model, and other documentation.