From: Andi Kleen <ak@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: piet@bluelane.com, "Amit S. Kale" <amitkale@linsyssoft.com>,
"Vladimir A. Barinov" <vbarinov@ru.mvista.com>,
Andrew Morton <akpm@osdl.org>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: linux-2.6 x86_64 kgdb issue
Date: Thu, 1 Jun 2006 00:59:17 +0200 [thread overview]
Message-ID: <200606010059.17859.ak@suse.de> (raw)
In-Reply-To: <20060531223515.GE31210@smtp.west.cox.net>
On Thursday 01 June 2006 00:35, Tom Rini wrote:
> On Wed, May 31, 2006 at 11:01:56PM +0200, Andi Kleen wrote:
> > On Wednesday 31 May 2006 17:03, Tom Rini wrote:
> > > On Wed, May 31, 2006 at 09:13:53AM +0200, Andi Kleen wrote:
> > >
> > > [snip]
> > >
> > > > Yes because you if modular works you don't need to build it in.
> > > >
> > > > Modular was working at some point on x86-64 for kdb and the original 2.6
> > > > version of kgdb was nearly there too.
> > >
> > > FWIW, the only change the current version of kgdb makes that would
> > > prevent it from being totally modular is the debugger_active check in
> >
> > Can you post the patch and a description?
>
> The change is a simple if (atomic_read(&debugger_active)) return right
> at the start. And I'm embarrased to say the change predates me on the
> project so I'm not 100% sure on the lineage and it might be totally
> bogus now.
And why do you need it? Where does the debugger call might sleep?
-Andi
next prev parent reply other threads:[~2006-05-31 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <446E0B4B.9070003@ru.mvista.com>
[not found] ` <200605241240.05313.amitkale@linsyssoft.com>
[not found] ` <4474A1D0.30807@ru.mvista.com>
[not found] ` <200605251207.27699.amitkale@linsyssoft.com>
2006-05-31 4:45 ` linux-2.6 x86_64 kgdb issue Piet Delaney
2006-05-31 5:50 ` Andi Kleen
2006-05-31 6:46 ` Piet Delaney
2006-05-31 7:13 ` Andi Kleen
2006-05-31 8:39 ` Piet Delaney
2006-05-31 9:41 ` Andi Kleen
2006-05-31 15:03 ` Tom Rini
2006-05-31 21:01 ` Andi Kleen
2006-05-31 22:35 ` Tom Rini
2006-05-31 22:59 ` Andi Kleen [this message]
2006-05-31 22:52 ` Piet Delaney
2006-05-31 23:03 ` Piet Delaney
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=200606010059.17859.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=amitkale@linsyssoft.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=trini@kernel.crashing.org \
--cc=vbarinov@ru.mvista.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.