Arm Community
Site
Search
User
Site
Search
User
Support forums
Architectures and Processors forum
How does ARM11 respond to a non-secure interrupt in secure mode?
Jump...
Cancel
State
Accepted Answer
+2
person also asked this
people also asked this
Locked
Locked
Replies
2 replies
Subscribers
351 subscribers
Views
5817 views
Users
0 members are here
Arm11
Interrupt
Options
Share
More actions
Cancel
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
How does ARM11 respond to a non-secure interrupt in secure mode?
Dong Luo
over 12 years ago
Note: This was originally posted on 19th March 2009 at
http://forums.arm.com
Hi All,
Assuming that ARM11 is running a secure process and receives a non-secure IRQ or FIQ, how does ARM11 respond to a non-secure interrupt? What should hardware do? And, what should software do? How does ARM11 guarantee that data of secure world not expose to the non-secure interrupt? Can anybody clarify the above questions? Thanks.
Top replies
Peter Harris
over 12 years ago
+1
verified
Note: This was originally posted on 19th March 2009 at http://forums.arm.com It depends on the configuration of the Secure Configuration Register set by the Secure World code, and the status of the I and...
Parents
0
unclep unclep
over 12 years ago
Note: This was originally posted on 20th March 2009 at
http://forums.arm.com
The key point is that *all* non-secure software (including all non-secure interrupt handlers) must be executed in the non-secure state so that the all non-secure code has no access to secure code or data. Well-written secure software (including the secure monitor) can ensure that this is that case (using the techniques described by isogen74).
One convenient policy is to dedicate IRQs to the nornal world, and to dedicate FIQs to the secure world. This allows the routing to be simple and efficient, going through the secure monitor only when necessary.
Cancel
Vote up
0
Vote down
Cancel
Reply
0
unclep unclep
over 12 years ago
Note: This was originally posted on 20th March 2009 at
http://forums.arm.com
The key point is that *all* non-secure software (including all non-secure interrupt handlers) must be executed in the non-secure state so that the all non-secure code has no access to secure code or data. Well-written secure software (including the secure monitor) can ensure that this is that case (using the techniques described by isogen74).
One convenient policy is to dedicate IRQs to the nornal world, and to dedicate FIQs to the secure world. This allows the routing to be simple and efficient, going through the secure monitor only when necessary.
Cancel
Vote up
0
Vote down
Cancel
Children
No data