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
  • #2755
Closed
Open
Issue created Dec 11, 2017 by Administrator@rootContributor

Add a flag to drcachesim to set cache warmup by loaded fraction

Created by: snehasish

drcachesim currently supports cache warm up by absolute number of references. We would like to support cache warmup determined by what fraction of the cache has been loaded -- eg "the cache is warm once 90% of its blocks have been loaded".

We determine the loaded fraction of the cache hierarchy by enumerating valid blocks in the last level cache only.

Implementation:

  1. Add warmup fraction knob to simulator_t
  2. Add counter num_valid_blocks to caching_device_t. Count of valid blocks are maintained by incrementing on load miss. This counter will need to be decremented on a) flush b) coherence invalidations (#1726 (closed))
  3. Check loaded fraction to determine warmup reached in cache_simulator_t::process_memref. Only use the fraction from llcache as we are simulating a two level hierarchy with a single last level cache (#1715 (closed)).
Assignee
Assign to
Time tracking