public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: Carsten Emde <C.Emde@osadl.org>
Cc: Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: How to find long execution times in kernel threads?
Date: Tue, 30 Apr 2013 20:02:23 +0200	[thread overview]
Message-ID: <5180072F.7010102@meduna.org> (raw)
In-Reply-To: <517FF6B1.9050204@osadl.org>

On 30.04.2013 18:52, Carsten Emde wrote:

> Sure, record everything (trace-cmd record -e all) and analyze the
> traces.

Well, the problem is that with record -e all I get 20 ms instead
of 1 ms, so I'd say Mr. Heisenberg laughs at me loudly here ;)

Thanks for the pointer anyway, I'll try to thoroughly read
the available documentation and come up with some sane set
of filters to start with.

Thanks
-- 
                                      Stano


  reply	other threads:[~2013-04-30 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 13:48 How to find long execution times in kernel threads? Stanislav Meduna
2013-04-30 16:52 ` Carsten Emde
2013-04-30 18:02   ` Stanislav Meduna [this message]
2013-05-01  3:58     ` Ashoka K
2013-05-01  7:37     ` Carsten Emde
2013-05-01  8:19       ` Stanislav Meduna

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=5180072F.7010102@meduna.org \
    --to=stano@meduna.org \
    --cc=C.Emde@osadl.org \
    --cc=linux-rt-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