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
If a trace is recorded using a counter as clock, the scaling value to seconds must be given manually as it is not part of the trace (at least from what I could find only the clock name can be extracted), similarly to what one does with trace-cmd:
trace-cmd report --ts2secs <Hz>
Not sure how this could be implemented in the UI, maybe a an entry in the context menu along with Apply Time Offset..., e.g. Apply Time Conversion... ?
I'm willing to work on this as I have some interest in it.
Any suggestions/pointers are appreciated :-).
The text was updated successfully, but these errors were encountered:
If a trace is recorded using a counter as clock, the scaling value to seconds must be given manually as it is not part of the trace (at least from what I could find only the clock name can be extracted), similarly to what one does with
trace-cmd
:Not sure how this could be implemented in the UI, maybe a an entry in the context menu along with
Apply Time Offset...
, e.g.Apply Time Conversion...
?I'm willing to work on this as I have some interest in it.
Any suggestions/pointers are appreciated :-).
The text was updated successfully, but these errors were encountered: