From: Keith Owens <kaos@ocs.com.au>
To: "Amit S. Kale" <kgdb@vsnl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: announce: kgdb 1.5 with reworked buggy smp handling
Date: Sat, 30 Mar 2002 11:17:21 +1100 [thread overview]
Message-ID: <330.1017447441@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 29 Mar 2002 20:33:19 +0530." <3CA48237.EA4D3F08@vsnl.net>
On Fri, 29 Mar 2002 20:33:19 +0530,
"Amit S. Kale" <kgdb@vsnl.net> wrote:
>Keith Owens wrote:
>>
>> On Fri, 29 Mar 2002 16:01:36 +0530,
>> "Amit S. Kale" <kgdb@vsnl.net> wrote:
>> >kgdb 1.5 at http://kgdb.sourceforge.net/
>> >
>> >smp handling is completely reworked. Previous kgdb had a bug
>> >which caused it to hang when a processor spun with
>> >interrupts disabled and another processor enters kgdb. kgdb
>> >now uses nmi watchdog for holding other processors while
>> >a machine is in kgdb.
>>
>> IA64 disabled spin loops ignore NMI :(.
>
>Thanks for the info.
>
>Isn't there any way get into an interrupt disabled spinning
>processor on an ia64 smp machine?
Only via an INIT interrupt. But that is also used to initialise a cpu
at startup, INIT interrupts go through PAL and SAL and have side
effects. I don't use them for kdb, they are too heavy.
For more background, see the thread "Replacements for local_irq_xxx()"
https://external-lists.vasoftware.com/archives//linux-ia64/2001-May/thread.html
prev parent reply other threads:[~2002-03-30 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 10:31 Amit S. Kale
2002-03-29 10:59 ` Keith Owens
2002-03-29 15:03 ` Amit S. Kale
2002-03-30 0:17 ` Keith Owens [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=330.1017447441@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kgdb@vsnl.net \
--cc=linux-kernel@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 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®