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

FTrace: support timebase conversion (equivalent of trace-cmd's --ts2secs HZ option) #33

Open
fabrizioiannetti opened this issue Jun 5, 2024 · 1 comment
Assignees

Comments

@fabrizioiannetti
Copy link
Contributor

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 :-).

@MatthewKhouzam
Copy link
Contributor

Hi, I am sorry it was so long to reply... there are some things that could be done.

  1. file creation time is not great
  2. we can store a time offset in the experiment
  3. you can add a uftrace or other trace with proper time, and take the same offset.

The problem is ftrace uses clock_monotonic. And clock_realtime is the one with the day. You would need to correlate the two.

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

No branches or pull requests

3 participants