Hi Olivier,
1. When I type git log in TF-A, here is the first info
commit 0aa70f4c4c023ca58dea2d093d3c08c69b652113 Merge: 8909fa9bb ffb07b043 Author: Madhukar Pappireddy madhukar.pappireddy@arm.com Date: Thu Feb 25 22:03:24 2021 +0000
Merge "plat/qemu: trigger reboot with secure pl061" into integration
2. When I type git log in Hafnium, here is the first info
commit aa336106d2feb7b9af3d7e3eec1294af27c35da0 Author: J-Alves joao.alves@arm.com Date: Mon Mar 1 13:02:45 2021 +0000
FF-A: FFA_MSG_SEND_DIRECT_REQ with invalid IDs
A call to FFA_MSG_SEND_DIRECT_REQ with invalid VM IDs should return error with code FFA_INVALID_PARAMETERS.
Change-Id: Iedfa173b37857f6f0b7297b6be012c51c51b169a Signed-off-by: J-Alves joao.alves@arm.com
3. I don't know how to check whether the Hafnium enable VHE in secure world. But I can see the current EL of Cactus SP (from TF-A-TESTS) is EL1. Should I provide other information?
Sincerely, Wang
Olivier Deprez Olivier.Deprez@arm.com 于2021年12月14日周二 01:29写道：
Hi,
Can you provide the base TF-A commit hash you use when building?
Out of curiosity do you enable VHE in the SWd/SPM?
Regards, Olivier. ________________________________ From: Hafnium hafnium-bounces@lists.trustedfirmware.org on behalf of Chenxu Wang via Hafnium hafnium@lists.trustedfirmware.org Sent: 13 December 2021 17:34 To: hafnium@lists.trustedfirmware.org hafnium@lists.trustedfirmware.org Subject: [Hafnium] A problem about assert failed in TF-A
Hi all, I am running Hafnium on FVP, with Cactus SP in SEL1 and KVM VHE enabled. Sometimes I send the "FFA_MSG_SEND_DIRECT_REQ" smc call in KVM (I fill 0x8400006f in x0, then VMID and SP ID in x1, let x2 as 0). It says assert failed, like this:
ASSERT: lib/el3_runtime/aarch64/context_mgmt.c:651 BACKTRACE: START: assert 0: EL3: 0x4005cac 1: EL3: 0x400323c 2: EL3: 0x400620c 3: EL3: 0x400e180 4: EL3: 0x4005a94 BACKTRACE: END: assert
I notice that when services/std_svc/spmd/spmd_main.c sends the FFA call (from NS to S) via "spmd_smc_forward(smc_fid, secure_origin,x1, x2, x3, x4, handle)", it will go to cm_el1_sysregs_context_restore(secure_state_out) and cm_el2_sysregs_context_restore(secure_state_out), then it will assert the cm_get_context(). it gets the NULL context, so assert failed.
Such assert is NOT ALWAYS failed, but I still want to solve this problem.
Since I have modified many lines of code in Hafnium and Cactus SP, I cannot show them here. Can you give me some advice on debugging? e.g., where should I check? -- Hafnium mailing list Hafnium@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/hafnium