-
Notifications
You must be signed in to change notification settings - Fork 13
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
Switch back to Counter based SpinLockIRQ #534
Open
kitlith
wants to merge
13
commits into
sunriseos:master
Choose a base branch
from
kitlith:recursive_irq_guard
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Commits on Oct 29, 2019
-
Revert "Go back to backup/restore SpinLockIRQ system"
This reverts commit e850a89.
Configuration menu - View commit details
-
Copy full SHA for 20ad4b8 - Browse repository at this point
Copy the full SHA 20ad4b8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6efa7ea - Browse repository at this point
Copy the full SHA 6efa7eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for de68901 - Browse repository at this point
Copy the full SHA de68901View commit details -
Configuration menu - View commit details
-
Copy full SHA for 692738d - Browse repository at this point
Copy the full SHA 692738dView commit details
Commits on Oct 31, 2019
-
This was interesting to figure out. In short, when a scheduler based process switch occurs, there is a lock held exclusively for enabling and disabling interrupts. This lock is not dropped before the process switch. If this is not the first time this process is run, it evens out by dropping the copy of this lock held by the 'new' process. However, if it is *not* the first time the process is run, there is no lock, and the counter never gets decremented. This commit fixes the issue by decrementing the counter in the new process right before the iret which reenabled interrupts.
Configuration menu - View commit details
-
Copy full SHA for f583a67 - Browse repository at this point
Copy the full SHA f583a67View commit details -
Preform ALL checks in try_lock.
Forgot to copy paste after fixing issues in lock. Doesn't seem to be used early enough to matter, but in case it ever is...
Configuration menu - View commit details
-
Copy full SHA for 495cb50 - Browse repository at this point
Copy the full SHA 495cb50View commit details -
Configuration menu - View commit details
-
Copy full SHA for c62dc63 - Browse repository at this point
Copy the full SHA c62dc63View commit details -
Configuration menu - View commit details
-
Copy full SHA for f104aec - Browse repository at this point
Copy the full SHA f104aecView commit details
Commits on Nov 2, 2019
-
Looks like when I went looking for examples, I found the wrong example.
Configuration menu - View commit details
-
Copy full SHA for 0936063 - Browse repository at this point
Copy the full SHA 0936063View commit details -
Move Safety comments inside the unsafe blocks.
It's funny, I could've sworn there was already some tool for this, but couldn't find it when I went to look for it. *shrug*
Configuration menu - View commit details
-
Copy full SHA for 0d026af - Browse repository at this point
Copy the full SHA 0d026afView commit details
Commits on Nov 3, 2019
-
Configuration menu - View commit details
-
Copy full SHA for a203fb5 - Browse repository at this point
Copy the full SHA a203fb5View commit details
Commits on Nov 9, 2019
-
Configuration menu - View commit details
-
Copy full SHA for d854a1f - Browse repository at this point
Copy the full SHA d854a1fView commit details -
Co-Authored-By: Robin Lambertz <github@roblab.la>
Configuration menu - View commit details
-
Copy full SHA for 9ebe582 - Browse repository at this point
Copy the full SHA 9ebe582View commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.