Skip to content

Conversation

@jserv
Copy link
Collaborator

@jserv jserv commented Nov 2, 2025

The function was attempting to access n_pages directly on mmu_cache_set_t structures, which don't have this member. The correct access path is cache_load[set].ways[way].n_pages for the 8-set × 2-way architecture.

The fix ensures all 16 load cache entries and 16 store cache entries are properly checked during range invalidation operations (e.g., SFENCE.VMA).


Summary by cubic

Fixed mmu_invalidate_range to correctly handle 8×2 set-associative load/store caches by iterating over sets and ways. Ensures SFENCE.VMA and range invalidations clear all relevant entries and prevent stale translations.

  • Bug Fixes
    • Use cache_*[set].ways[way].n_pages instead of accessing n_pages on mmu_cache_set_t.
    • Invalidate all 16 load and 16 store entries; fetch cache handled separately.

Written for commit ebe49d9. Summary will update automatically on new commits.

The function was attempting to access n_pages directly on mmu_cache_set_t
structures, which don't have this member. The correct access path is
cache_load[set].ways[way].n_pages for the 8-set × 2-way architecture.

The fix ensures all 16 load cache entries and 16 store cache entries
are properly checked during range invalidation operations (e.g.,
SFENCE.VMA).
cubic-dev-ai[bot]

This comment was marked as resolved.

@jserv jserv merged commit 51e1115 into master Nov 2, 2025
11 checks passed
@jserv jserv deleted the fix-build branch November 2, 2025 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants