All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: piet@bluelane.com, Tom Rini <trini@kernel.crashing.org>,
	Dave Jiang <djiang@mvista.com>,
	linux-kernel@vger.kernel.org, sshtylyov@ru.mvista.com,
	Andrew Morton <akpm@osdl.org>,
	George Anzinger <george@wildturkeyranch.net>,
	"David O'Brien" <obrien@freebsd.org>
Subject: Re: Permanent Kgdb integration into the kernel - lets get with it.
Date: Tue, 17 Apr 2007 20:45:03 +0200	[thread overview]
Message-ID: <200704172045.03743.ak@suse.de> (raw)
In-Reply-To: <20070417113016.1f0812c7.randy.dunlap@oracle.com>


> Is there any movement on this?

I'm open to reasonable patches for the hooks at least. If that is done
then the actual kgdb code can be reviewed and considered eventually too. 

But just having the hooks in would make it easy enough to use anyways 
(no patching, just dropping in of new files, or even loading of it as a
module into any kernel)

When I did the original x86-64 kgdb port this worked nicely --
kgdb could work with just the standard die notifiers and a simple
change in the serial console code.

The recent kgdb seems to need much more changes again though.

However every time when I suggested this (fixing the hooks first
and submitting the really needed changes piece by piece)
there didn't seem to be any interest from the various kgdb maintainers.

So my impression currently is that they're not interested in merging.

Another problem is that kgdb is moving more and more away from
mainline by adding various weird hacks and workarounds in random
code that just make  merging harder.

Before anything could be considered for merging that all would
need to be cleaned up.

-Andi

  parent reply	other threads:[~2007-04-17 18:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 20:45 [PATCH] x86_64 RESTORE_CONTEXT missing '\n' Dave Jiang
2007-03-08 17:14 ` Andi Kleen
2007-03-08 17:44   ` Dave Jiang
2007-03-08 18:37     ` Andi Kleen
2007-03-08 18:49       ` Tom Rini
2007-03-08 22:24         ` Permanent Kgdb integration into the kernel - lets get with it Piet Delaney
2007-04-17 18:30           ` Randy Dunlap
2007-04-17 18:37             ` Sergei Shtylyov
2007-04-17 18:42               ` Randy Dunlap
2007-04-17 18:45                 ` Sergei Shtylyov
2007-04-17 18:45             ` Andi Kleen [this message]
2007-04-20 16:20               ` Robin Holt
2007-04-20 22:51             ` Piet Delaney
2007-04-20 23:34               ` Andrew Morton
2007-04-21  9:48                 ` Andi Kleen
2007-04-24  4:02                   ` Permanent Kgdb integration into the kernel - lets get with it. (Dave: How do FreeBSD folks maintain the KGDB stub?) Piet Delaney
2007-03-08 22:36         ` [PATCH] x86_64 RESTORE_CONTEXT missing '\n' Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2007-04-06 22:03 [PATCH 6/13] maps#2: Move the page walker code to lib/ Matt Mackall
2007-04-11  6:35 ` Nick Piggin
2007-04-17 20:45   ` Matt Mackall
2007-04-17 21:26     ` Permanent Kgdb integration into the kernel - lets get with it Jason Wessel
2007-04-17 22:09       ` Andi Kleen

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=200704172045.03743.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=djiang@mvista.com \
    --cc=george@wildturkeyranch.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=obrien@freebsd.org \
    --cc=piet@bluelane.com \
    --cc=randy.dunlap@oracle.com \
    --cc=sshtylyov@ru.mvista.com \
    --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.