All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Pavel Machek <pavel@suse.cz>,
	akpm@osdl.org, george@mvista.com, amitkale@emsyssoft.com,
	Andi Kleen <ak@suse.de>,
	jim.houston@comcast.net,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BitKeeper repo for KGDB
Date: Mon, 9 Feb 2004 11:38:28 -0600	[thread overview]
Message-ID: <20040209173828.GG2315@waste.org> (raw)
In-Reply-To: <20040209155013.GF5219@smtp.west.cox.net>

On Mon, Feb 09, 2004 at 08:50:13AM -0700, Tom Rini wrote:
> On Sun, Feb 08, 2004 at 07:29:51PM -0600, Matt Mackall wrote:
> > On Fri, Feb 06, 2004 at 04:02:54PM -0700, Tom Rini wrote:

> > >  	if (!netpoll_trap() && len == 8 && !strncmp(msg, "$Hc-1#09", 8))
> > > -		printk(KERN_CRIT "Someone is trying to attach\n");
> > > -//		kgdb_schedule_breakpoint();
> > > +		breakpoint();
> > >  
> > >  	for (i = 0; i < len; i++) {
> > > -		if (msg[i] == 3)	/* Check for ^C? */
> > > -			printk(KERN_CRIT "Someone is trying to ^C?\n");
> > > -//			kgdb_schedule_breakpoint();
> > > +		if (msg[i] == 3)
> > > +			breakpoint();
> > 
> > The kgdb_schedule_breakpoint stuff in -mm didn't just appear to make
> > things more complicated, it is in fact necessary. You cannot
> > reasonably expect to break deep inside the network stack IRQ handler
> > and then send more packets out the same interface. Expect especially
> > nasty results on SMP. It only works for the serial case because that
> > path is a priori known to be lockless.
> 
> Ah, hmm...  I don't suppose there's any way to do this w/o touching
> every arch's do_IRQ, is there?

Probably not. On the other hand, it provides yet more motivation for
an irq handling refactoring in 2.7.

-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

  reply	other threads:[~2004-02-09 17:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 18:40 BitKeeper repo for KGDB Tom Rini
2004-01-27 19:31 ` Sam Ravnborg
2004-01-27 19:46   ` Dave Jones
2004-01-27 20:07 ` Chris Wright
2004-01-27 21:02   ` Tom Rini
2004-01-28  9:50     ` Dave Jones
2004-01-28 16:51 ` Pavel Machek
2004-01-28 17:05   ` Tom Rini
2004-01-28 17:44     ` Pavel Machek
2004-01-28 17:56       ` Tom Rini
2004-01-28 18:04         ` Pavel Machek
2004-02-06 22:35         ` Tom Rini
2004-02-06 22:55           ` Pavel Machek
2004-02-06 23:02             ` Tom Rini
2004-02-09  1:29               ` Matt Mackall
2004-02-09 15:50                 ` Tom Rini
2004-02-09 17:38                   ` Matt Mackall [this message]
2004-02-10  7:57                     ` Amit S. Kale
2004-02-10  8:27                       ` Amit S. Kale
2004-02-10 19:26                         ` Tom Rini
2004-02-11 14:35                           ` Amit S. Kale
2004-02-10  8:46                       ` Dave Jones
2004-02-10 19:22                         ` Tom Rini
2004-02-10 19:23                           ` Dave Jones
2004-01-30 18:18 ` Tom Rini

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=20040209173828.GG2315@waste.org \
    --to=mpm@selenic.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=amitkale@emsyssoft.com \
    --cc=george@mvista.com \
    --cc=jim.houston@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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 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.