Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

misc: Hotfix v24.1.0.2 #1964

Merged
merged 3 commits into from
Feb 12, 2025
Merged

Conversation

BobbyRBruce
Copy link
Member

This adds #1930 as a hotfix to gem5 v24.1.0

aarmejach and others added 3 commits February 1, 2025 23:34
Currently the RubySystem pointer is set when set_tbe is performed, which
effectively clears the NetDest objects from the TBE (if any). This is
fine if the TBE has been just allocated before set_tbe is called (no
NetDest info in the TBE). However, the CHI protocol has an action
(RestoreFromHazard) that performs a set_tbe over a TBE that had already
been set, i.e., it already has valid NetDest data.

This patch sets the RubySystem pointer when the TBE is allocated, which
is more natural and follows the style already adopted in the
PerfectCacheMemory class (gem5#1864).

Co-authored-by: Adrià Armejach <[email protected]>
@BobbyRBruce BobbyRBruce added mem General Memory Systems (e.g., XBar, Packet) mem-ruby Ruby caches, structures, and protocols labels Feb 2, 2025
@BobbyRBruce BobbyRBruce merged commit 186a913 into gem5:stable Feb 12, 2025
38 checks passed
@BobbyRBruce BobbyRBruce deleted the hotfix-v24-1-0-2 branch February 12, 2025 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mem General Memory Systems (e.g., XBar, Packet) mem-ruby Ruby caches, structures, and protocols
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants