From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
Tom Rini <trini@kernel.crashing.org>
Subject: Fixed broken x86_64
Date: Thu, 4 Mar 2004 20:06:55 +0530 [thread overview]
Message-ID: <200403042006.55161.amitkale@emsyssoft.com> (raw)
Hi,
I am attempting to fix broken x86_64: kgdb_connected is zero when kgdb
connects to gdb. This comes through a debug exception.
I am checking in this patch to fix it for uniprocessor systems. I still have
to think about smp system.
-Amit
@@ -556,13 +566,15 @@
+{
+ struct die_args *d = ptr;
+
-+ if (!kgdb_connected || (cmd == DIE_DEBUG && user_mode(d->regs)))
++ if (cmd == DIE_DEBUG && user_mode(d->regs))
+ return NOTIFY_DONE;
+ if (cmd == DIE_NMI_IPI) {
-+ if (atomic_read(debugger_active))
++ if (atomic_read(&debugger_active))
+ return NOTIFY_BAD;
-+ } else if ((*linux_debug_hook)(d->trapnr, d->signr, d->err,
d->regs))
-+ return NOTIFY_BAD; /* skip */
++ } else {
++ CHK_DEBUGGER(d->trapnr, d->signr, d->err, d->regs,);
++ return NOTIFY_BAD;
++ }
+
+ return NOTIFY_DONE;
+}
reply other threads:[~2004-03-04 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200403042006.55161.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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