🐛 Fix dynamic handling of top-level interrupt initialization#937
Merged
Conversation
Problem: - The cached state of IRQs which are statically enabled is not properly initialized. Solution: - For IRQs which have been statically enabled, make sure the cached register state is also set to enabled.
Problem: - Interrupt register values are "cached", but it isn't really a cache: it's written through immediately and serves to avoid RMW. "Cache" implies things that don't occur; a better way to describe this is a shadow value. Solution: - Rename `cached_*` to `shadow_*` for the dynamic interrupt manager.
elbeno
force-pushed
the
fix-dynamic-init-cache
branch
from
June 30, 2026 17:53
e571e82 to
33ae5b8
Compare
mjcaisse-intel
approved these changes
Jun 30, 2026
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
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.
Problem:
initialized.
Solution:
state is also set to enabled.