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

[pull] stable from gem5:stable #6

Merged
merged 4 commits into from
Feb 12, 2025
Merged

[pull] stable from gem5:stable #6

merged 4 commits into from
Feb 12, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 12, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

aarmejach and others added 4 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 (#1864).

Co-authored-by: Adrià Armejach <[email protected]>
This adds #1930 as a hotfix to gem5 v24.1.0
@pull pull bot added the ⤵️ pull label Feb 12, 2025
@pull pull bot merged commit 186a913 into ZTHKaiYuan:stable Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants