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

feat(TopDown): add TopDown PMU Events #4122

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

feat(TopDown): add TopDown PMU Events #4122

wants to merge 4 commits into from

Conversation

sinceforYy
Copy link
Contributor

@sinceforYy sinceforYy commented Jan 3, 2025

This PR adds hardware synthesizable three-level categorized TopDown performance counters.
Level-1: Retiring, Frontend Bound, Bad Speculation, Backend Bound.
Level-2: Fetch Latency Bound, Fetch Bandwidth Bound, Branch Missprediction, machine clears, Core Bound, Memory Bound.
Leval-3: L1 Bound, L2 Bound, L3 Bound, Mem Bound, Store Bound.

@sinceforYy sinceforYy changed the title Feat(TopDown): add TopDown PMU Events feat(TopDown): add TopDown PMU Events Jan 3, 2025
@sinceforYy sinceforYy marked this pull request as ready for review January 6, 2025 01:43
@Ivyfeather
Copy link
Member

remember to merge the changes in submodules into their masters first

a PR in XiangShan must have all its submodules checked-out to their masters (otherwise CI would fail)

@eastonman
Copy link
Member

I don't understand. This PR does not distinguish frontend latency from bandwidth. Frontend latency is a counter that increases by 1 every time the decode bandwidth is not full. This does not make sense to me.

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.

5 participants