[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tracecompass-dev] Enabling Events
|
You need to write them following the TSDL grammar. Here [1] is the official specification. The examples section is very complete.
However, if you don't need to do anything too complex, you might be able to just copy paste the definition of a Linux Kernel event in the metadata file, set a new id field for it, and modify it with your own parameters (is similar to a c struct). Your custom events must use the corresponding id in the metadata file.
You might find useful this minimal example application [2] that writes a "fake" Linux Kernel trace.
[1] -
https://diamon.org/ctf/#examples[2] -
https://gitlab.com/aleixrocks/lttng_ctf_fakerOn February 7, 2020 8:12:39 PM GMT+09:00, tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx> wrote:
Hi,
May I know how to add definitions of my own events i.e. non-standard Linux kernel trace events into the trace metadata file?
Thanks
(Please refer the discussion below)
Hi!
I'm not an expert on this, but I recently did something similar.
Is your conversion script writing non-standard Linux Kernel events in
the CTF file? If so, Have you added the definition of your own events
into the trace metadata file?
On Wed, Jan 29, 2020 at 12:04:36PM +0530, tracecompass developer discussions wrote:
> Hi community,
>
> I have written a python script to convert a certain type of trace into CTF.
> The file is opening in trace compass but the PID, TID and Prio fields are
> not visible. However, if I change the name of my events to *sched_switch*,
> these fields become visible. I read somewhere that we need to enable
> events. I need to know how I can enable my events and how *sched_switch* event
> got enabled.
>
> Thanks and regards,
> Basavaraj M. Hi!
I'm not an expert on this, but I recently did something similar.
Is your conversion script writing non-standard Linux Kernel events in
the CTF file? If so, Have you added the definition of your own events
into the trace metadata file?
On Wed, Jan 29, 2020 at 12:04:36PM +0530, tracecompass developer discussions wrote:
> Hi community,
>
> I have written a python script to convert a certain type of trace into CTF.
> The file is opening in trace compass but the PID, TID and Prio fields are
> not visible. However, if I change the name of my events to *sched_switch*,
> these fields become visible. I read somewhere that we need to enable
> events. I need to know how I can enable my events and how *sched_switch* event
> got enabled.
>
> Thanks and regards,
> Basavaraj M.
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/tracecompass-dev
http://bsc.es/disclaimer
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tracecompass-dev
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
