Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How to trap/route unallocated instruction exception to EL3 #702

Open
caihuali95 opened this issue Jan 15, 2020 · 2 comments
Open

Comments

@caihuali95
Copy link

I wonder whether it is possible to trap/route unallocated instruction exception to EL3?
Unallocated instruction exception is a synchronous exception. But I failed to catch this exception in EL3 even if I set SCR_EL3.EA = 1.

If it is impossible to do that, is there any document explaining which synchronous exceptions can be trapped into EL3 while others can not?

@ssg-bot
Copy link

ssg-bot commented Jan 15, 2020

Hello @caihuali95!

Thank you for raising an issue for Trusted Firmware-A.

The TF-A project has now migrated to www.trustedfirmware.org. This issue tracker will still remain accessible for some time, but only for historical reasons. From now on you should raise any new issues on trustedfirmware.org.

How do I raise issues for TF-A?

Please use our new issue tracking board. For this you just need to login with your existing GitHub account. We also have a guide to help you raise the issue with the appropriate labels and tags. This way it will be easier for both you and us to track and address the issue most effectively.

What if I face any problems?

You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing you in trustedfirmware.org!

The Trusted Firmware-A team

@mcejp
Copy link

mcejp commented Jan 20, 2023

@caihuali95
Out of curiosity, have you ever figured out how to trap EL1 synchronous exceptions to EL3? From my reading of the manuals there is no way to do it -- other than using EL3 superpowers to control the code in EL1's exception vectors.
The SCR_EL3.EA bit seems to only concern SError (system error, not synchronous error) and External Abort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants