Skip to content

cpu-o3: change intel fewops from 4 to 8 #758

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.

Sign up for GitHub

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 1 commit into
base: xs-dev
Choose a base branch
from
Open

cpu-o3: change intel fewops from 4 to 8 #758

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/cpu/o3/issue_queue.hh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ class Scheduler : public SimObject
CPU* cpu;
MemDepUnit* memDepUnit;
LSQ* lsq;
const int intel_fewops = 4;
const int intel_fewops = 8;
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep FEW-op threshold aligned with configured issue width

Raising intel_fewops to a hardcoded 8 makes exec_stall_cycle count cycles as “few uops” even when narrower cores are fully utilized, which skews the Topdown breakdown (coreBound/memoryBound) that is derived from these counters in src/cpu/o3/cpu.cc (lines 503-521) and normalized by cpu->issueWidth (lines 479-490). This is a regression for any config with issue width below 8 (for example, the decodeWidth = 4 Xiangshan ECore configs), where full-issue cycles will now be misclassified as stalls.

Useful? React with 👍 / 👎.

bool old_disp = false;
const int intRegfileBanks;

Expand Down