From: Mandeep Singh Baines <msb@google.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, rientjes@google.com,
mbligh@google.com, thockin@google.com, akpm@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] softlockup: detect bottom-half lockups
Date: Thu, 15 Jan 2009 06:04:55 -0800 [thread overview]
Message-ID: <20090115140454.GH4722@google.com> (raw)
In-Reply-To: <20090114080640.GA19116@elte.hu>
Stumbled upon ftrace tracepoints while writing this patch. Should
make life a lot easier for debugging latency issues.
bhlockup should complement ftrace. Once you've found that there's a
problem, tracing can be a big help in debugging. But assertions are
nice for finding problems you didn't know exist.
Ingo Molnar (mingo@elte.hu) wrote:
>
> * Mandeep Singh Baines <msb@google.com> wrote:
>
> > The feature should be useful to real-time developers and developers of
> > network and other high-performance drivers.
>
> hm, did you know about the ftrace latency tracers:
>
> config IRQSOFF_TRACER
> bool "Interrupts-off Latency Tracer"
>
> config PREEMPT_TRACER
> bool "Preemption-off Latency Tracer"
>
> config SCHED_TRACER
> bool "Scheduling Latency Tracer"
>
> PREEMPT_TRACER would have shown you that softirqs-off section very nicely.
>
> (And if you also enable the function tracer then not just the latency
> endpoint is shown, but also all the function calls that happened in the
> critical section.)
>
> Ingo
prev parent reply other threads:[~2009-01-15 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 7:04 [PATCH] softlockup: detect bottom-half lockups Mandeep Singh Baines
2009-01-14 8:06 ` Ingo Molnar
2009-01-15 14:04 ` Mandeep Singh Baines [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=20090115140454.GH4722@google.com \
--to=msb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rientjes@google.com \
--cc=thockin@google.com \
/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.