EE: vtlb handler for writes to IOP mem #11933
Merged
Conversation
This file contains 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
JordanTheToaster
approved these changes
Oct 21, 2024
|
Actually I take it back :^) |
|
Fixed |
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.
Description of Changes
Puts EE writes to IOP mem through a handler that calls the write function for IOP mem. This ensures we clear IOP code blocks when EE writes to it.
Rationale behind Changes
The b000p demo (see #3983) has a LoadModuleBuffer patch that is applied with memcpy from the EE. Previously we didn't properly invalidate the cache when this was applied.
Suggested Testing Steps
Check that b000p works and nothing broke 🤷