-
Notifications
You must be signed in to change notification settings - Fork 68
2 taken v8 #693
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
Open
jensen-yan
wants to merge
23
commits into
xs-dev
Choose a base branch
from
2-taken-v8
base: xs-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
2 taken v8 #693
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
3d3031d
cpu-o3: pred: functional implementation of 2-taken.
boran-xu 3de33af
cpu-o3: pred: implemented realistic 2-taken.
boran-xu 7d4da8b
cpu-o3: pred: add performance counter for 2taken.
boran-xu a6a3761
cpu-o3: pred: clear ubtb during squashing:
boran-xu 845e030
cpu-o3: pred: update ras predictor during second FB prediction
boran-xu 5b698bf
ci: modify ci for testing purpose of this branch
boran-xu f23f3eb
cpu-o3: pred: statistics for 2 taken training condition
boran-xu bbe9e90
test: the upperbound of 2taken when ubtb is large enough
boran-xu b84ba79
cpu-o3: pred: allow alwaysTaken branch as 2nd pred of 2taken.
boran-xu e60e6ff
cpu-o3: Enable mBTB updates for 2nd prediction fetch blocks
boran-xu 26c0814
cpu-o3: Restore ABTB accuracy under 2-taken
boran-xu 8d972ae
cpu-o3: pred: check histInfo match in ubtb replacement.
boran-xu a676b77
cpu-o3: pred: added ratio stats for 2 taken
boran-xu 995a626
cpu-o3: pred: give more intuitive name to methods
boran-xu 5d0b801
cpu-o3: pred: add ubtb training perf counters
boran-xu e222f42
cpu-o3: pred: dff buffer stores s3_pred instead of finalPred
boran-xu efe74b2
cpu-o3: pred: fixed bug where 2taken training gets skipped
boran-xu bb8a86f
Revert "test: the upperbound of 2taken when ubtb is large enough"
boran-xu 24f38a2
cpu-o3: pred: 2taken support pt_2nd
boran-xu 976d7fb
ci: for testing purpose, remember to revert
boran-xu be558d5
cpu-o3: pred: refactor, add 2taken stats.
boran-xu a032b26
cpu-o3: pred: reduce the frequency of clearing ubtb 2ndBrInfo
boran-xu 1564af5
cpu-o3: pred: update 2 taken doc
boran-xu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
8 changes: 3 additions & 5 deletions
8
.github/workflows/gem5-perf.yml → .../workflows/gem5-ideal-btb-perf-2taken.yml
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,14 +1,12 @@ | ||
| name: gem5 Performance Test | ||
| name: gem5 Ideal BTB Performance Test (2Taken) | ||
|
|
||
| on: | ||
| push: | ||
| branches: [ xs-dev ] | ||
| pull_request: | ||
| branches: [ xs-dev ] | ||
| branches: [ 2-taken-v8 ] | ||
|
|
||
| jobs: | ||
| perf_test: | ||
| uses: ./.github/workflows/gem5-perf-template.yml | ||
| with: | ||
| script_path: ../kmh_6wide.sh | ||
| script_path: ../kmh_v3_btb_2taken.sh | ||
| benchmark_type: "spec06-0.8c" |
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: OpenXiangShan/GEM5
Length of output: 180
🏁 Script executed:
Repository: OpenXiangShan/GEM5
Length of output: 92
🏁 Script executed:
Repository: OpenXiangShan/GEM5
Length of output: 9501
Unify attribute naming for 2-taken prediction across FTB and BTB.
enableTwoTaken(FTB, line 373) andenable2Taken(BTB, line 385) are separate attributes in different classes serving the same semantic purpose. The inconsistent naming—one spelling out "Two" and the other using the digit "2"—risks confusion during maintenance and development. Consider standardizing to a single naming convention across both implementations.🤖 Prompt for AI Agents