blob: afef9dad53aec4bb324b1a2e4a351079b8258c48 [file] [log] [blame]
Soby Mathewb4c6df42022-11-09 11:13:29 +00001.. SPDX-License-Identifier: BSD-3-Clause
2.. SPDX-FileCopyrightText: Copyright TF-RMM Contributors.
3
4############################
5Change-log and Release notes
6############################
7
8******
9v0.1.0
10******
11
12- First TF-RMM source release aligned to `RMM Beta0 specification`_.
13 The specified interfaces : Realm Management Interface (RMI) and
14 Realm Service Interface (RSI) are implemented which can attest
15 and run Realm VMs as described by the `Arm CCA`_ Architecture.
16
17=================
18Upcoming features
19=================
20
21- Support SVE, Self-Hosted Debug and PMU in Realms
22- Support LPA2 for Stage 2 Realm translation tables.
23- Threat model covering RMM data flows.
24- Enable Bounded Model Checker (CBMC) for source analysis.
25- Unit test framework based on :ref:`RMM Fake host architecture`.
26
27============================
28Known issues and limitations
29============================
30
31The following is a list of issues which are expected to be fixed in the future
32releases of TF-RMM :
33
34- The size of ``RsiHostCall`` structure is 256 bytes in the implementation
35 and aligns to `RMM Beta1 specification`_ rather than the 4 KB size
36 specified in `RMM Beta0 specification`_.
37
38- The RSI_IPA_STATE_GET command returns error ``RSI_ERROR_INPUT`` for a
39 `destroyed` IPA instead of emulating data abort to Host.
40
41- The `RMM Beta0 specification`_ does not require to have a CBOR bytestream
42 wrapper around the cca-platform-token and cca-realm-delegated-token, but
43 the RMM implementation does so.
44
45---------------------------
46
47.. _RMM Beta0 specification: https://developer.arm.com/documentation/den0137/1-0bet0/?lang=en
48.. _RMM Beta1 specification: https://developer.arm.com/documentation/den0137/1-0bet1/?lang=en
49.. _Arm CCA: https://www.arm.com/architecture/security-features/arm-confidential-compute-architecture