From: Tom Rini <trini@kernel.crashing.org>
To: Chris Wright <chrisw@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][0/6] A different KGDB stub
Date: Fri, 13 Feb 2004 12:04:53 -0700 [thread overview]
Message-ID: <20040213190453.GA1564@smtp.west.cox.net> (raw)
In-Reply-To: <20040213105838.F14506@build.pdx.osdl.net>
On Fri, Feb 13, 2004 at 10:58:38AM -0800, Chris Wright wrote:
> * Tom Rini (trini@kernel.crashing.org) wrote:
> > On Wed, Feb 11, 2004 at 04:27:56PM -0800, Andrew Morton wrote:
> > > CONFIG_KGDB_SYSRQ (Just turn it on by default?)
> > >
> > > I have never used (or, as far as I know, needed) any of the above.
> >
> > I think CONFIG_KGDB_SYSRQ can die since with the 8250 and enet drivers
> > you can try and connect at any point, which will schedule a breakpoint
> > and you can get in like that. As for NO_KGDB_CPUS, I'm not entirely
> > certain why this can't go away and there'd be an array of NR_CPUS in
> > size.
>
> Using kgdboe I've had numerous times where it gets a bit wedged and
> only sysrq-g could get the breakpoint.
Alright. We can just always have it on SYSRQ+KGDB then.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-13 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 0:02 Tom Rini
2004-02-12 0:27 ` Andrew Morton
2004-02-12 16:52 ` Tom Rini
2004-02-13 18:58 ` Chris Wright
2004-02-13 19:04 ` Tom Rini [this message]
2004-02-17 22:02 Tom Rini
2004-02-17 22:36 ` Andrew Morton
2004-02-17 22:52 ` Pavel Machek
2004-02-18 4:56 ` Amit S. Kale
2004-02-18 5:05 ` Andrew Morton
2004-02-18 12:56 ` Pavel Machek
2004-02-18 13:15 ` Amit S. Kale
2004-02-18 18:48 ` Pavel Machek
2004-02-18 18:21 ` Tom Rini
2004-02-19 4:46 ` Amit S. Kale
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=20040213190453.GA1564@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--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®