public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Matt Mackall <mpm@selenic.com>
Cc: George Anzinger <george@mvista.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@zip.com.au>
Subject: Re: kgdb cleanups
Date: Sat, 10 Jan 2004 20:34:06 +0100	[thread overview]
Message-ID: <20040110193406.GA241@elf.ucw.cz> (raw)
In-Reply-To: <20040110175607.GH18208@waste.org>

Hi!

> > >>>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've sent Amit the start of an plug interface for abstracting the
> > >communication layer. Should be relatively painless and allow for
> > >starting sessions on the interface of your choice.
> > >
> > May I see?
> 
> Here's the interface plus the eth side of it:

Does it work with those patches? (Amid's version does not seem to work
over ethernet).
								Pavel


-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2004-01-10 19:35 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
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 [this message]
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=20040110193406.GA241@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@zip.com.au \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox