-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Optimize interrupt return code on ARC. #2716
Labels
area: ARC
ARC Architecture
area: Kernel
Enhancement
Changes/Updates/Additions to existing features
priority: low
Low impact/importance bug
Milestone
Comments
by Deli Niu: From the view of PnP, it could be verified by latency benchmark.
New: Old: |
by Mark Linkmeyer: Fixing incorrect priority |
zephyrbot
added
priority: low
Low impact/importance bug
area: ARC
ARC Architecture
area: Kernel
Enhancement
Changes/Updates/Additions to existing features
labels
Sep 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: ARC
ARC Architecture
area: Kernel
Enhancement
Changes/Updates/Additions to existing features
priority: low
Low impact/importance bug
Reported by Benjamin Walsh:
There are too many pushes and pops on the stack when deciding which thread to run when exiting an interrupt. Also, see if _is_next_thread_current and _get_next_ready_thread could not be folded together. Or maybe write _is_next_thread_current in assembly.
(Imported from Jira ZEP-1230)
The text was updated successfully, but these errors were encountered: