From: Matteo Bertolino <matteo.bertolino@huawei.com>
To: "linux-trace-users@vger.kernel.org" <linux-trace-users@vger.kernel.org>
Subject: Format of trace.dat flyrecord section
Date: Wed, 15 Jun 2022 15:18:41 +0000 [thread overview]
Message-ID: <e3287c4e7ae2407f873bedf74df9651c@huawei.com> (raw)
Dear community,
[Goal] I am trying to understand more about tracing. In one of my experiments, I decided to try to write my own trace.dat file (with some dummy entries).
To do that, I am following the documentation for a "version-7 .dat" provided in https://github.com/rostedt/trace-cmd/blob/master/Documentation/trace-cmd/trace-cmd.dat.v7.5.txt ,
and trying to looking at the code of libtraceevent, trace-cmd and kernelshark. I use kernelshark to be sure I am writing a good trace.
[Context] I managed to write a complete header (I double-checked checking in strategical points in trace-cmd, kernelshark and libtraceevent code). In this header, I have three sections:
- Section 0, with options 16 (header_infos), option 8 (in which I stated to have a single CPU), and option 3. The latter states that I have a cpu whose data starts at offset 4096 of the trace.
- Section 16: in which I transfers the information of `header_page` and `header_event` files.
- Section 3: the flyrecord section, whose header is followed by a padding to be one-page aligned. After the padding, there should be the CPU datas.
Yet another check of the header's correctness are outputs of commands `trace-cmd dump --flyrecord -i mytrace.dat` and `trace-cmd dump --summary -i ../mytrace_v7.dat`.
[Problem] The problems occur there. I don't manage to get the format of flyrecords.
I understood that timestamps need to follow the structure of ringbuffers (those expressed in `header_event` file), so 5 bits for the type_len, 27 for the time_delta, and an u32 array[].
But, kernelshark entries contains also: timestamp, CPUs, PID, EVENT, TASK, LATENCY and "INFO".
Through flybuffer schema, I can only provide TIMESTAMP divided by CPUs, but where do I take other fields?
In addition to this, I didn't understand how I can provide multiple entries.
Thanks for you possible help,
Matteo
next reply other threads:[~2022-06-15 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 15:18 Matteo Bertolino [this message]
2022-06-16 4:25 ` Format of trace.dat flyrecord section Tzvetomir Stoyanov
2022-06-16 13:00 ` Steven Rostedt
[not found] ` <20220616090237.2c9dda8b@gandalf.local.home>
2022-06-16 13:03 ` Steven Rostedt
2022-06-17 13:08 ` Matteo Bertolino
2022-06-17 13:10 ` Matteo Bertolino
2022-06-17 15:25 ` Tzvetomir Stoyanov
2022-06-20 15:59 ` Matteo Bertolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3287c4e7ae2407f873bedf74df9651c@huawei.com \
--to=matteo.bertolino@huawei.com \
--cc=linux-trace-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).