Hi,

I have below queries regarding nested sError handling in TF-A, please help.

1. While handling exceptions in EL3, sError is almost unmask most of the time. Any specific reason to keep sError unmasked?

For example, while handing nested sError, we can keep sError masked in serror_sp_elx. So that no further sError comes to EL3.

And unmask sError when returning to lower ELs. Do you think this will create any problem in the system?

2. In system, sError can happen at any time. At EL3, we have nested sError handling in serror_sp_elx.

                Do you think we should have similar nested sError handling in serror_sp_el0? If not, what is the reason?

3. Double fault will always lead to unhandled exception.
1. Can someone help define double fault scenario?
2. What is the purpose of this patch - https://github.com/ARM-software/arm-trusted-firmware/commit/c72200357aed49fd51dc21e45d4396f5402df811

                Is purpose only to save esr_el3 register?

Thanks

Regards,

Jaiprakash

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.