Hi all,
I want to find a register which will specifically control the Secure
Stage 2 translation. But Arm document does not provide it.
I find that a register, called HCR_EL2, will control the Stage 2
translation. But the document didn't mention which secure type it will
control. Thus, does the Non-secure hypervisor (like KVM) influence the
Secure Stage-2 address translation? For example, disabling it through
HCR_EL2?
Sincerely,
WANG Chenxu
Hi all,
I am not sure whether it is OK to ask the question here, but I still
wish you can help me address the problem.
I used to test Hafnium with FVP, and the Linux kernel is provided by
arm-reference-platform. Recently I want to test something on an OPTEE
kernel (rather than a cactus OS). But, since the provided linux kernel
is a bit old (v5.3), its /drivers/tee/optee will not send FF-A calls.
I find that Linux introduces FF-A ABI to OP-TEE driver since v5.16,
which is a relatively new kernel. Previously I download the Linux
kernel here ( https://git.linaro.org/landing-teams/working/arm/kernel-release.git),
but they only provide old kernels. I also try to replace the "linux"
directory with the upstream Linux v5.17 source code, and use the guide
here (https://community.arm.com/oss-platforms/w/docs/459/modify-linux-kernel-conf…)
to compile. But the source seems to be inconsistent with the
arm-reference-platforms.
Can someone help me?
Sincerely,
WANG Chenxu
Hi all,
I want to boot one or more OPTEE on SEL1, with using Hafnium (v2.4) on
SEL2 and TF-A (v2.4) on EL3, and Arm FVP. Before I can boot multiple
Cactus SP, but I can find little infos about booting OP-TEE.
Can you provide some useful guide?
Sincerely,
WANG Chenxu
