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

Queued prefetcher only looks into Data TLB (DTB), which makes it inefficient with I-side prefetchers #766

Open
giactra opened this issue Jan 12, 2024 · 0 comments
Labels

Comments

@giactra
Copy link
Contributor

giactra commented Jan 12, 2024

Describe the bug
As reported in one of the gem5 slack channels (https://gem5-workspace.slack.com/archives/C03K26BGTKL/p1703584762742109) the queued prefetcher translates request with the BaseMMU::Read argument 1.
This automatically informs the MMU to look into the D-TLB 2 and it works ok for D-side prefetchers.
This is not the case for I-side ones.
In that scenario, the D-TLB lookup will likely miss and (unless there is a second level TLB) will request the translation though the page table walker. This means:

  1. Unnecessary PTW affecting prefetch timing
  2. Increased simulation time.

I believe the solution would be to tag a prefetcher accordingly so that either BaseMMU::Read or BaseMMU::Execute will be used.

Host Operating System
All

Host ISA
All

@giactra giactra added the bug label Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant