core: priority inheritance protocol with mutex overlap support#7461
Closed
bergzand wants to merge 11 commits intoRIOT-OS:masterfrom
Closed
core: priority inheritance protocol with mutex overlap support#7461bergzand wants to merge 11 commits intoRIOT-OS:masterfrom
bergzand wants to merge 11 commits intoRIOT-OS:masterfrom
Conversation
bergzand
changed the title
miri64
added
Area: core
miri64
added
the
Process: needs >1 ACK
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions. |
stale
bot
added
the
State: stale
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This is mostly an academic exercise to see if it is possible to pass the test from #7455.
Each mutex stores the highest priority among tasks waiting in the mutex queue.
By building a linked list of all locked mutexes, it is possible for a thread, when unlocking a mutex, to restore its priority to the highest priority among the locked mutexes (and its own configured priority).
The test from #7455 somehow still fails, but I don't see immediately why, the output looks correct to me 😃.