Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #4996
Closed
Open
Issue created Jul 06, 2021 by Al Grant@algrant-arm

drcachesim should support any associativity

drcachesim currently only supports power-of-2 associatvities. This is not an inherent property of set-associative caches, and it is not uncommon for production silicon to feature e.g. 3-way or 5-way for L1, or perhaps 12-way or 24-way for outer caches. The size is related to the associativites and hence also might not be a power of 2, e.g. 48K for a 3-way L1.

For correlation against this silicon, and to get more data points in cache studies, it would be useful to support these associativities.

This looks fairly straightforward, it needs some minor adjustments to option validation, and uses of assoc_bits or masking need to change.

Assignee
Assign to
Time tracking