Hi Olivier,

Thanks. That makes sense. Correct, the FVP version I'm using is 11.12.38. I'll take a look further into the issue and see if I can fix it since I'm already on it, unless somebody else can get to it before I do.

Thanks Raghu

-----Original Message----- From: Olivier Deprez Olivier.Deprez@arm.com Sent: Tuesday, December 8, 2020 8:49 AM To: raghu.ncstate@icloud.com Cc: hafnium@lists.trustedfirmware.org Subject: Re: [Hafnium] Memory sharing test failures with FVP

Hi Raghu,

Are you referring to the gcc build flavor with which FVP is built (Linux64_GCC-6.4)? FVP version should look more like 11.12.38 if you do: ./FVP_Base_RevC-2xAEMv8A --version

Thus far Hypervisor has been validated using qemu through the Hafnium builder (using the kokoro/build.sh script): https://ci.trustedfirmware.org/job/hafnium-build-test-review/ Even though the build script offers the capability, there is currently no automation with FVP for the Hypervisor test suite.

We've used FVP for the secure-world / SPMC validation, but that's a different test suite within TF-A CI.

In other words, it's possible you find problems running FVP on the Hypervisor test suite, and that's worth fixing.

Regards, Olivier.

________________________________________ From: Hafnium hafnium-bounces@lists.trustedfirmware.org on behalf of Raghu Krishnamurthy via Hafnium hafnium@lists.trustedfirmware.org Sent: 08 December 2020 17:20 To: hafnium@lists.trustedfirmware.org Subject: [Hafnium] Memory sharing test failures with FVP

Hi All,

I'm seeing test failures when I use FVP and run the memory_share test suite(in primary_with_secondaries_test) on the 6.4 version of AEM FVP(works on qemu, don't know if it works on AEM FVP 4.9). Is anybody else aware of these failures and working on fixing them? Appears to be alignment faults. Test logs for some of the tests show a stage 2 fault at 0x200 but that is really because service_vm3 does not install an exception handler in EL1 and when the data abort is taken in EL1, VBAR_EL1 is not set up, and hafnium gets a stage 2 fault, and injects unknown exception to EL1, which faults again in hafnium again and so on.

Easy to repro:

Update test/hftest/hftest.py to use the 6.4 version of FVP and run:

timeout --foreground 300s ./test/hftest/hftest.py --driver=fvp --out out/reference/aem_v8a_fvp_clang --out_initrd out/reference/aem_v8a_fvp_vm_clang --tfa --log out/reference/kokoro_log hafnium --initrd test/vmapi/primary_with_secondaries/primary_with_secondaries_test --suite memory_sharing

Thanks Raghu

-- Hafnium mailing list Hafnium@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/hafnium