Hi Jack,
These are interesting use cases and would help other platform owners too IMO.
Like the idea of introducing platform hooks in the abort path. Overall the design philosophy of Hafnium is not to add platform code, so one approach might be to introduce SMC FID for the platform path instead.
For involving SP/SPMC in the fatal event handling path, have you evaluated the SP lifecycle messages? The FFA ALP5 spec chapter 18.9 has these new states that could be used for this use case, AFAICT.
Hope this helps.
-Varun
From: Jack Suann via Hafnium hafnium@lists.trustedfirmware.org Date: Wednesday, 2 September 2026 at 02:04 To: hafnium@lists.trustedfirmware.org hafnium@lists.trustedfirmware.org Subject: [Hafnium] Improving abort handling in Hafnium
External email: Use caution opening links or attachments
Hi everyone,
As you may be aware, at Qualcomm we've been looking into various enhancements we'd like to make to Hafnium; one recent area we've identified for improvement is the fatal error handling which currently just spins on panic / abort.
To start with, we're looking at making abort() stop other CPUs and DMA, as well as introduce a platform hook to allow for platform-specific handling before propagating the error to the SPMD via FFA_ABORT; please let us know if this sound reasonable and if you have any other suggestions for improving this abort handling.
Beyond this we are also interested in improving the fatal error handling in the secure world more broadly. In particular, when a fatal event is received by TF-A then we want to give the SPMC and its SPs the opportunity to run so they can perform their own error handling before reset.
Is there a suitable framework for supporting this kind of error / reset handling? One existing mechanism for this is SDEI, though on the TF Discord it was mentioned that this has been deprecated (at least for hardware events) in favor of more recent extensions such as FEAT_NMI; would these newer extensions be suitable for software events as well? How can event handling be supported on platforms that lack these newer extensions?
Also, what would be the impact of this kind of event handling on the FF-A specification?
Thanks in advance for your support on this issue.
Regards, Jack Suann -- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org