You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: