mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace based hard lockup detector
Date: Mon, 19 Jan 2009 07:59:01 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0901190757330.17050@gandalf.stny.rr.com> (raw)
In-Reply-To: <4973cff5.05a0660a.650c.2f54@mx.google.com>



On Sun, 18 Jan 2009, Frederic Weisbecker wrote:

> Like the NMI watchdog, this feature try to detect hard lockups by
> lurking at the non-progress of the timer interrupts.
> 
> You can enable it at boot time by passing the ftrace_hardlockup parameter.
> I plan to add a debugfs file to enable/disable at runtime.
> 
> When a hardlockup is detected, it will print a backtrace. Perhaps it
> would be good to print the locks held from lockdep too?
> 
> It only support x86 for the moment, because a kind of generic timer interrupt
> counter is needed on all archs to have it generic.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>

Hi Frederic,

This seems like a rewrite of the NMI lockup code. In my debugging, I 
simply put ftrace_dump in the NMI lockup, which gives me a ftrace dump as 
soon as NMI detects a lockup. I'm a bit confused at what this gives us 
over that?

-- Steve

       reply	other threads:[~2009-01-19 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4973cff5.05a0660a.650c.2f54@mx.google.com>
2009-01-19 12:59 ` Steven Rostedt [this message]
2009-01-19 13:04   ` Ingo Molnar
2009-01-19 13:18     ` Steven Rostedt
2009-01-19 13:24       ` Ingo Molnar
2009-01-19 13:25       ` Frédéric Weisbecker

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=alpine.DEB.1.10.0901190757330.17050@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®