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

ARC: timeslice not reset on interrupt-induced swap #3670

Closed
zephyrbot opened this issue Jun 1, 2017 · 6 comments
Closed

ARC: timeslice not reset on interrupt-induced swap #3670

zephyrbot opened this issue Jun 1, 2017 · 6 comments
Assignees
Labels
area: ARC ARC 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

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-2234)

@zephyrbot zephyrbot added priority: low Low impact/importance bug area: ARC ARC Architecture bug The issue is a bug, or the PR is fixing a bug labels Sep 23, 2017
@galak
Copy link
Collaborator

galak commented Nov 20, 2018

@ruuddw, @vonhost do you know if this is still an issue?

@ruuddw
Copy link
Member

ruuddw commented Nov 21, 2018

Don't know. '_update_time_slice_before_swap' doesn't exist anymore after the timer refactoring. That did introduce other problems for ARC due to bugs in the 'legacy' support: #10747, #11129, #11170
@andyross : appreciate your guidance here on if this is still relevant?

@vonhust
Copy link

vonhust commented Nov 21, 2018

I think it's not issue now, at least no test cases report. #10747, #11129, #11179, I think, it's not related to this

@ruuddw
Copy link
Member

ruuddw commented Nov 21, 2018

Issue #3668 (GH-3668 mentioned above) states there is no testcase for this issue, so no testcase reports doesn't say much...

@galak
Copy link
Collaborator

galak commented Dec 6, 2018

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

@andyross
Copy link
Contributor

andyross commented Dec 6, 2018

Yeah, this got fixed as part of the timer rework. The relevant code is in the generic kernel, not the per-arch timer driver. It works the same everywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ARC ARC Architecture bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

5 participants