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
  • Merge requests
  • !5704

i#2039 trace trim, part 4: Clamp timestamps

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Derek Bruening requested to merge i2039-nop-mode into master Oct 25, 2022
  • Overview 19
  • Commits 6
  • Pipelines 0
  • Changes 6

Moves the timestamp+cpu headers to be added at buffer creation time instead of at buffer output time.

Makes instru_t::frozen_timestamp_ use release-acquire semantics and sets it for -align_endpoints at detach time.

Adds a 'minimum timestamp' recorded at post-attach time. At buffer output time, we examine the buffer's timestamp and if it was from before the minimum, we replace it with the current (not the minimum) timestamp.

Tested on a large app where these changes result in much tighter timestamps matching the burst period.

Issue: #2039 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: i2039-nop-mode