-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
xtensa: remove up_set_current_regs/up_current_regs #14960
Conversation
[Experimental Bot, please feedback here] This PR appears to partially meet the NuttX requirements. While it provides a reason for the change, it lacks crucial details. Missing Information:
Example of Improvements: Summary: Impact:
Testing:
Testing logs before change:
Testing logs after change:
By providing this level of detail, the PR will be much easier to review and understand. It demonstrates a clear understanding of the change and its implications. |
I'll trigger our internal CI. Please wait it to merge it. |
We've found an issue with the backtrace dump feature applied to this PR. The backtrace for the task's assertion does not work as expected with our test application (please check below) when
and then, run
The test application:
|
cc984f4
to
73bd040
Compare
fixed |
Thanks. I'll trigger it again |
Xtensa is failing to build with
|
reason: up_set_current_regs initially had two functions: 1: To mark the entry into an interrupt state. 2: To record the context before an interrupt/exception. If we switch to a new task, we need to store the upcoming context regs by calling up_set_current_regs(regs). Currently, we record the context in other ways, so the second function is obsolete. Therefore, we need to rename up_set_current_regs to better reflect its actual meaning, which is solely to mark an interrupt. Signed-off-by: hujun5 <[email protected]>
This commit fixes the regression from apache#14865 Signed-off-by: hujun5 <[email protected]>
@tmedicci does this patch pass your internal ci? |
fixed |
I've just tested it again. It's now passing all tests. Thanks! |
Summary
reason:
up_set_current_regs initially had two functions:
1: To mark the entry into an interrupt state.
2: To record the context before an interrupt/exception. If we switch to a new task, we need to store the upcoming context regs by calling up_set_current_regs(regs).
Currently, we record the context in other ways, so the second function is obsolete. Therefore, we need to rename up_set_current_regs to better reflect its actual meaning, which is solely to mark an interrupt.
Impact
xteansa
Testing
ci ostest