public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@zip.com.au>
Subject: Re: kgdb cleanups
Date: Fri, 09 Jan 2004 13:54:12 -0800	[thread overview]
Message-ID: <3FFF2304.8000403@mvista.com> (raw)
In-Reply-To: <20040109183826.GA795@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
> No real code changes, but cleanups all over the place. What about
> applying?
> 
> Ouch and arch-dependend code is moved to kernel/kgdb.c. I'll probably
> do x86-64 version so that is rather important.
> 
> 								Pavel
A few comments:

I like the code seperation.  Does it follow what Amit is doing?  It would be 
nice if Amit's version and this one could come together around this.

I don't think we want to merge the eth and regular kgdb just yet.  I would, 
however, like to keep eth completly out of the stub.  Possibly a new module 
which just takes care of steering the I/O to the correct place.

I think we might want to try the bad sys call one more time.  If it triggers, a 
kernel fix is in order.  I don't see the point of removing it.  After all, the 
disable/enable on preempt really should be paired such that we never leave the 
kernel with a preempt count.

I have new dwarft stuff.  I actually have debug records that allow bt through 
interrupt code.  Working on the spin lock loops.  It is fine to drop these at 
this point as the new ones will replace them anyway.



-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2004-01-09 21:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 18:38 kgdb cleanups Pavel Machek
2004-01-09 21:41 ` Andrew Morton
2004-01-09 21:54 ` George Anzinger [this message]
2004-01-10  4:47   ` Matt Mackall
2004-01-10  8:12     ` George Anzinger
2004-01-10 17:56       ` Matt Mackall
2004-01-10 19:34         ` Pavel Machek
2004-01-10 19:37           ` Matt Mackall
2004-01-12  5:41         ` George Anzinger
2004-01-12  6:49           ` Matt Mackall
2004-01-12  9:45             ` Pavel Machek
2004-01-13 20:54               ` George Anzinger
2004-01-13 21:00                 ` Pavel Machek
2004-01-12 13:53             ` Amit S. Kale
2004-01-13 21:20               ` George Anzinger
2004-01-14 13:20                 ` Amit S. Kale
2004-01-14 20:40                   ` George Anzinger
2004-01-13 20:53             ` George Anzinger
2004-01-14 13:04               ` Amit S. Kale
2004-01-14 20:35                 ` George Anzinger
2004-01-10 15:15   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-12-28 14:13 Pavel Machek
2003-12-28 20:14 ` Robert Walsh

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=3FFF2304.8000403@mvista.com \
    --to=george@mvista.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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