From: Jason Wessel <jason.wessel@windriver.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@linaro.org>,
<linaro-kernel@lists.linaro.org>, Mike Travis <travis@sgi.com>,
Randy Dunlap <rdunlap@infradead.org>,
Dimitri Sivanich <sivanich@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>,
<kgdb-bugreport@lists.sourceforge.net>
Subject: Re: [RFC PATCH] kgdb: Timeout if secondary CPUs ignore the roundup
Date: Tue, 1 Jul 2014 09:22:17 -0500 [thread overview]
Message-ID: <53B2C419.4090706@windriver.com> (raw)
In-Reply-To: <1404224174-25024-1-git-send-email-daniel.thompson@linaro.org>
On 07/01/2014 09:16 AM, Daniel Thompson wrote:
> Currently if an active CPU fails to respond to a roundup request the
> CPU that requested the roundup will become stuck. This needlessly
> reduces the robustness of the debugger.
>
> This patch introduces a timeout allowing the system state to be examined
> even when the system contains unresponsive processors. It also modifies
> kdb's cpu command to make it censor attempts to switch to unresponsive
> processors and to report their state as (D)ead.
It seems reasonable to allow entry on the master core because there certainly could be useful information to be had with respect to how you got there in the first place, but I wonder about the case for resuming the system. In general if you couldn't sync in the the first place, the system is dead. My opinion is that we probably should explicitly disallow a resume or single step at that point.
Jason.
next prev parent reply other threads:[~2014-07-01 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:16 [RFC PATCH] kgdb: Timeout if secondary CPUs ignore the roundup Daniel Thompson
2014-07-01 14:22 ` Jason Wessel [this message]
2014-07-02 14:12 ` [PATCH v2] " Daniel Thompson
2014-08-18 15:01 ` [RESEND PATCH v2 3.17rc1] " Daniel Thompson
2014-11-11 17:50 ` [PATCH v3] " Daniel Thompson
2014-12-10 20:46 ` Daniel Thompson
2015-01-07 16:15 ` [RESEND PATCH v3 3.19-rc2] " Daniel Thompson
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=53B2C419.4090706@windriver.com \
--to=jason.wessel@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=daniel.thompson@linaro.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rdunlap@infradead.org \
--cc=sivanich@sgi.com \
--cc=travis@sgi.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.