Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: gbastien@versatic.net (Genevieve Bastien)
Subject: [lttng-dev] Mixing kernel and userspace traces in a single events editor view
Date: Fri, 3 Aug 2018 18:34:01 -0400	[thread overview]
Message-ID: <2f00819a-0f8e-9412-4e05-3743a6236d06@versatic.net> (raw)
In-Reply-To: <1533304674046.28750@BlackBox.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]

Hi John,


In Trace Compass, you can import/open your traces as an "experiment".
See the documentation here for more information on experiments:
http://archive.eclipse.org/tracecompass/doc/stable/org.eclipse.tracecompass.doc.user/Trace-Compass-Main-Features.html#Creating_an_Experiment


Regards,

Geneviève


On 2018-08-03 09:57 AM, John O'Sullivan wrote:
>
> Hi,
>
>
> I using trace compass on an embedded target, I have a sample
> application with some user space events and I am also collecting some
> kernel events.
>
> Is there some way in trace compass of looking at these in a single
> Events Editor view so that both kernel and Userspace events are
> interleaved with respect to time?
>
>
> The script I am using on my target is;
>
>
>  #!/bin/sh
> HOST_IP="10.xxx.xxx.xxx"
> #Create a session sending the data over the network to a listening host
> lttng create --set-url=net://$HOST_IP
> #Create one or more events
> lttng enable-event -u -a -c chan1
> lttng enable-event --kernel sched_switch,sched_process_fork
> #create an event for the logger
> lttng enable-event --kernel lttng_logger
> lttng start
> echo "Loading sample aplication" > /proc/lttng-logger
> /usr/bin/sample_application
> echo "unLoading sample aplication" > /proc/lttng-logger
> lttng destroy
>
>
> The resulting traces when opened only allows me to view kernel and UST
> on separate tabs
>
>
> regards
>
>
> John
>
>
> ------------------------------------------------------------------------
>
> This email and any files transmitted with it are confidential and are
> intended for the sole use of the individual to whom they are
> addressed. Black Box Corporation reserves the right to scan all e-mail
> traffic for restricted content and to monitor all e-mail in general.
> If you are not the intended recipient or you have received this email
> in error, any use, dissemination or forwarding of this email is
> strictly prohibited. If you have received this email in error, please
> notify the sender by replying to this email.
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20180803/70cb741c/attachment.html>


      reply	other threads:[~2018-08-03 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 13:57 John O'Sullivan
2018-08-03 22:34 ` Genevieve Bastien [this message]

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=2f00819a-0f8e-9412-4e05-3743a6236d06@versatic.net \
    --to=gbastien@versatic.net \
    /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