From: Gerrit Binnenmars <gerritbinnenmars@wanadoo.nl>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: CONFIG_CRITICAL_IRQSOFF_TIMING
Date: Tue, 30 Oct 2007 22:46:44 +0100 (CET) [thread overview]
Message-ID: <31957022.1615381193780804539.JavaMail.www@wwinf6102> (raw)
> Datum: 30/10/07 10:38 PM
> Van: "Daniel Walker"
> Aan: gerritbinnenmars@wanadoo.nl
> CC: linux-rt-users@vger.kernel.org
> Onderwerp : Re: CONFIG_CRITICAL_IRQSOFF_TIMING
>
> On Tue, 2007-10-30 at 22:26 +0100, Gerrit Binnenmars wrote:
>
> > Daniel, I first applied the rt patchset and then the LTTng patch
> > (http://ltt.polymtl.ca/lttng/patch-2.6.22.1-rt4-lttng-0.9.10.tar.gz).
> > Then LTT can be selected in the Instrumentation part of the config file.
> > further ltt-control is needed (http://ltt.polymtl.ca/lttng/ltt-control-0.43-10082007.tar.gz)
> >
> > The viewer is only working on i386 but that is not really a problem.
> >
> > So, I applied the available patches without doing anything special.
>
> Ok .
>
> > Is LTT causing troubles with the preempt_max_latency options?
>
> I doubt it .. I haven't used the histogram options in a month or so ..
> But if I remember correctly the value of preempt_max_latency is suppose
> to remain at zero .. Usually preempt_max_latency is used to prune off
> uninteresting latencies (ones under the max) but if you have the
> histogram option turn on then all latencies points need to be recorded.
> The data can be viewed in in /proc/latency_hist/ .. In 2.6.22 there is
> no way to reset the histograms for preempt off, or interrupts off
> timing.
Daniel,
Thanks for your suggestion. The latency_hist shows a max long value for the minimum latency.
All other values remain 0. I think the tracer is not running at all, but I am not sure.
I will remove the latency_hist option tomorrow and recheck preempt_max_latency.
Gerrit
>
> Daniel
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next reply other threads:[~2007-10-30 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 21:46 Gerrit Binnenmars [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-31 19:53 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-31 20:03 ` CONFIG_CRITICAL_IRQSOFF_TIMING Steven Rostedt
2007-10-30 21:26 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 21:32 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-30 21:09 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 21:05 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-30 20:52 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 20:56 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-31 0:17 ` CONFIG_CRITICAL_IRQSOFF_TIMING Steven Rostedt
2007-10-28 13:00 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-29 13:08 ` CONFIG_CRITICAL_IRQSOFF_TIMING 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=31957022.1615381193780804539.JavaMail.www@wwinf6102 \
--to=gerritbinnenmars@wanadoo.nl \
--cc=dwalker@mvista.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.