TranslationCPU: Always eventually handle IRQs #131
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.
If an interrupt is triggered while the CPU is stopped, then we don't do anything about it. However, this is the only chance we have to handle the rising edge of the incoming IRQ. If the interrupt controller tries to trigger a new interrupt after the CPU has been resumed, the GPIO will remember that it was already set and won't call OnGPIO. This will cause all further IRQs to be ignored.
Fix this by enqueuing deferred IRQs until the CPU is resumed (or one of the other conditions changes). This ensures that we eventually handle all calls to OnGPIO.
Fixes: 160f4d1 ("Initial commit of the Emul8 framework.")