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

Review relationship between local and global timestamps #12

Open
tmplt opened this issue Jan 26, 2022 · 1 comment
Open

Review relationship between local and global timestamps #12

tmplt opened this issue Jan 26, 2022 · 1 comment
Labels
investigate Further investigation required
Milestone

Comments

@tmplt
Copy link
Member

tmplt commented Jan 26, 2022

Current implementation assumes that local and global timestamps are sourced from the same clock. This is not neccesarily the case, and is platform dependent: global timestamps are sourced from a "global timestamp clock" and local timestamps can either be sourced from the async TPIU clock or the system processor clock.

We'll likely need to add some configuration options on how to interpret timestamp packets.

@tmplt tmplt added the investigate Further investigation required label Jan 26, 2022
@tmplt tmplt added this to the v1.0.0 milestone Jan 26, 2022
@tmplt tmplt modified the milestones: v1.0.0, v0.8.0 Mar 10, 2022
tmplt added a commit to tmplt/masters-thesis that referenced this issue Mar 10, 2022
@tmplt
Copy link
Member Author

tmplt commented Mar 10, 2022

Following from tmplt/masters-thesis@70ce53f it may be apt to inquire ARM whether the clock relationship should be interpreted as device-specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate Further investigation required
Projects
None yet
Development

No branches or pull requests

1 participant