Re: [PATCH] kernel-shark-2.alpha: Use new tracecmd API to open guest tracing file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 3.04.20 г. 20:12 ч., Tzvetomir Stoyanov wrote:
Maybe it has to be a bit more sophisticated. Does the "primary" stream
know how to recognize its "secondary" streams?

Yes, there are tracing IDs in both host and guest files. When these IDs match,
files are from a same tracing session.
I can add "parent_stream_id" member in "struct kshark_data_stream" and
initialize it
when reading the files, according to the trace IDs.

Not sure if this is the right place to put this information. I do not want to have "tep data" specific fields in "struct kshark_data_stream". Is it possible to have this mapping stored in in "struct tepdata_handle" instead.

Thanks!
Yordan



[Index of Archives]     [Linux USB Development]     [Linux USB Development]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux