mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@ezchip.com>
To: Jeff Merkey <linux.mdb@gmail.com>, <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Don Zickus <dzickus@redhat.com>,
	Ulrich Obergfell <uobergfe@redhat.com>,
	Aaron Tomlin <atomlin@redhat.com>, Michal Hocko <mhocko@suse.cz>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Tejun Heo <tj@kernel.org>,
	Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Subject: Re: [PATCH v2] Add hard/soft lockup debugger entry points
Date: Tue, 26 Jan 2016 12:22:35 -0500	[thread overview]
Message-ID: <56A7AB5B.2000000@ezchip.com> (raw)
In-Reply-To: <20160126170454.GA28216@localhost.localdomain>

On 01/26/2016 12:04 PM, Jeff Merkey wrote:
> This patch adds an export which can be set by system debuggers to direct
> the hard lockup and soft lockup detector to trigger a breakpoint exception
> and enter a debugger if one is active.  It is assumed that if someone
> sets this variable, then an breakpoint handler of some sort will be actively
> loaded or registered via the notify die handler chain.
>
> This addition is extremely useful for debugging hard and soft lockups
> real time and quickly from a console debugger.
>
> Signed-off-by: Jeff Merkey<linux.mdb@gmail.com>
> ---
>   kernel/watchdog.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)

You probably should reach out to someone who uses this stuff more
regularly - I actually wonder if the kgdb_breakpoint() API is the
right thing, though, not the internal arch_kgdb_breakpoint().

Of course any of these strategies also assume you are building
the kernel with CONFIG_KGDB set, and I'm pretty sure will cause
your build to fail if it isn't.  You likely need to guard this
stuff locally within watchdog.c for !CONFIG_KGDB.

-- 
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

  reply	other threads:[~2016-01-26 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 17:04 Jeff Merkey
2016-01-26 17:22 ` Chris Metcalf [this message]
2016-01-26 17:26   ` Jeff Merkey
2016-01-26 17:45 ` kbuild test robot
2016-01-26 18:46 ` kbuild test robot
2016-01-26 19:33   ` Jeff Merkey

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=56A7AB5B.2000000@ezchip.com \
    --to=cmetcalf@ezchip.com \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@gmail.com \
    --cc=mhocko@suse.cz \
    --cc=tj@kernel.org \
    --cc=uobergfe@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome