Re: [PATCH v13 00/48] arm64: Support for Arm CCA in KVM

[Gavin Shan]

Hi Steven,

On 3/21/26 2:45 AM, Steven Price wrote:
> On 19/03/2026 23:02, Mathieu Poirier wrote:

[...]

> > > The TF-RMM has not yet merged the RMMv2.0 support, so you will need to
> > > use the following branch:
> > >
> > > https://git.trustedfirmware.org/TF-RMM/tf-rmm.git topics/rmm-v2.0-poc
> >
> > This RMM version is expecting a RMM EL3 interface version of at least 2.0.  Do
> > you have a TF-A to use with it?
>
> You should be able to use the 'master' branch of the TF-A repository.
> For now you need to set RMM_V1_COMPAT=0 to enable 2.0 support.

In upstream TF-A repository [1], I don't see the config option 'RMM_V1_COMPAT'.
would it be something else?

[1] git@xxxxxxxxxx:ARM-software/arm-trusted-firmware.git    (branch: master)

I use the following command to build TF-A image. The RMM-EL3 compatible issue is
still seen.

    TFA_PATH=$PWD
    EDK2_IMAGE=${TFA_PATH}/../edk2/Build/ArmVirtQemuKernel-AARCH64/RELEASE_GCC5/FV/QEMU_EFI.fd
    RMM_IMAGE=${TFA_PATH}/../tf-rmm/build-qemu/Debug/rmm.img
    
    make CROSS_COMPILE=aarch64-none-elf-                               \
         PLAT=qemu ENABLE_RME=1 RMM_V1_COMPAT=0 DEBUG=1 LOG_LEVEL=40   \
         QEMU_USE_GIC_DRIVER=QEMU_GICV3                                \
         BL33=${EDK2_IMAGE} RMM=${RMM_IMAGE}                           \
         -j 8 all fip

Booting messages
================
INFO:    BL31: Initializing runtime services
INFO:    RMM setup done.
INFO:    BL31: Initializing RMM
INFO:    RMM init start.
ERROR:   RMM init failed: -2
WARNING: BL31: RMM initialization failed

Thanks,
Gavin