Skip to content

xtensa: timeslice not reset for interrupt-induced swaps #3669

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.

Sign up for GitHub

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

Jump to bottom
Closed
zephyrbot opened this issue Jun 1, 2017 · 2 comments
Closed

xtensa: timeslice not reset for interrupt-induced swaps #3669

zephyrbot opened this issue Jun 1, 2017 · 2 comments
Assignees
@andyross
Labels
area: Xtensa Xtensa Architecture bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Jun 1, 2017 •
edited
Loading

Reported by Andrew Boie:

If an interrupt induces a context switch, we need to call into _update_time_slice_before_swap. Test this with GH-3668

(Imported from Jira ZEP-2233)
@zephyrbot zephyrbot added priority: low Low impact/importance bug area: Xtensa Xtensa Architecture bug The issue is a bug, or the PR is fixing a bug labels Sep 23, 2017
@andrewboie andrewboie assigned andyross and unassigned andrewboie May 16, 2018
@galak
Copy link
Collaborator

galak commented Dec 6, 2018

Guys can you look at this and see if its still relevant?

@andyross
Copy link
Collaborator

andyross commented Dec 6, 2018

Just like #3670, fixed with the timer rework

@andyross andyross closed this as completed Dec 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andyross andyross

Labels
area: Xtensa Xtensa Architecture bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andyross @andrewboie @galak @zephyrbot