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

Value prediction development roadmap #188

Open
2 tasks
zybzzz opened this issue Oct 16, 2024 · 1 comment
Open
2 tasks

Value prediction development roadmap #188

zybzzz opened this issue Oct 16, 2024 · 1 comment

Comments

@zybzzz
Copy link
Contributor

zybzzz commented Oct 16, 2024

This is the roadmap for Value prediction development, refer to #181 for the general roadmap development of xs-gem5.

Value prediction roadmap

Benchmarks

  1. general: SPEC06
  2. specific: other domain-specific applications.

Evaluation Metrics

  1. SPEC06 weighted score and IPC speedup
  2. Value predictor accuracy rate
  3. Value predictor coverage rate

Development Purpose

The current expectation is to integrate the value predictor without massive changes to the microarchitecture. The primary goal of the current development of the value predictor is to integrate the stride-base value predictor for pre-RTL architecture exploration for kunminghu v3.

Development Details

value predictors

Prediction error strategy

  • pipeline flushing.(current implementation)
  • Add replay-buffer, re-issue from replay-buffer.

Develop branchs

  1. valuepred-base as a main branch of value prediction development.
  2. valuepred-(feature) develops different predictors as a downstream branch of valuepred-base.

Does valuepred-base need to be synchronized with the upstream branch xs-dev? Any ideas?

Future

  1. co-design with prefetch
  2. co-degisn with memory dependency prediction unit
@zybzzz
Copy link
Contributor Author

zybzzz commented Nov 21, 2024

@shinezyy @jensen-yan

Preliminary performance data for the value predictor is given, currently only overall scores are given, detailed data has not yet been analyzed. A 5KB stride predictor is given first, as there are still bugs associated with the current predictor design. In comparison, the performance yields a 42% miss, which is very bad. The exact reason for this is yet to be analyzed.

================ Overall baseline=================
Estimated overall score per GHz: 16.200665687457658
Estimated overall score @ 3.0GHz: 48.60199706237297

================ Overall with 5KB EStride VP=================
Estimated overall score per GHz: 9.19388382981961
Estimated overall score @ 3.0GHz: 27.581651489458828

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

No branches or pull requests

1 participant