linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: Still problem with red preempted boxes for tasks
Date: Wed, 3 Oct 2018 22:10:30 +0300	[thread overview]
Message-ID: <b1b4b516-9b6a-87ea-7755-4d1952ce0444@gmail.com> (raw)
In-Reply-To: <20181003144835.23f09933@gandalf.local.home>

Hi Steven,

Thanks a lot for this feedback!

I will try to fix this before the end of the week. Not sure I manage to 
understand what has to be done for the colors of the task plots but I 
guess you can show me at our next 1:1.

My talk tomorrow starts at 5 PM Sofia time (10 AM for you). I still 
don't have the link for the streaming but I hope to have it tomorrow.

cheers,
Yordan


On  3.10.2018 21:48, Steven Rostedt wrote:
> Hi Yordan,
> 
> While looking at my data, I found that the red empty boxes to represent
> preemption for task plots is still unreliable.
> 
> Down load this: http://rostedt.org/private/trace-views.tar.bz2
> 
> Then in the /tmp directory:
> 
>   /tmp$ tar xvf trace-views.tar.bz2
> 
> Start up KernelShark, and import view1.json. Notice the red preemption
> box and what tasks they are for. Then load view2.json and do the same,
> the view3.json, and that as well. You'll notice that each one gives
> different preemption boxes in the same location.
> 
> -- Steve
> 
> P.S. The session files really help with passing you debugging info like
> this :-)
> 

  reply	other threads:[~2018-10-04  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 18:48 Still problem with red preempted boxes for tasks Steven Rostedt
2018-10-03 19:10 ` Yordan Karadzhov (VMware) [this message]
2018-10-03 19:15   ` Steven Rostedt

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=b1b4b516-9b6a-87ea-7755-4d1952ce0444@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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).