mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Piet Delaney <piet@bluelane.com>
To: Andi Kleen <ak@suse.de>
Cc: Piet Delaney <piet@bluelane.com>,
	Tom Rini <trini@kernel.crashing.org>,
	"Amit S. Kale" <amitkale@linsyssoft.com>,
	"Vladimir A. Barinov" <vbarinov@ru.mvista.com>,
	Andrew Morton <akpm@osdl.org>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: linux-2.6 x86_64 kgdb issue
Date: Wed, 31 May 2006 15:52:25 -0700	[thread overview]
Message-ID: <1149115945.26542.208.camel@piet2.bluelane.com> (raw)
In-Reply-To: <200605312301.56452.ak@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

On Wed, 2006-05-31 at 23:01 +0200, Andi Kleen wrote:
> On Wednesday 31 May 2006 17:03, Tom Rini wrote:
> > On Wed, May 31, 2006 at 09:13:53AM +0200, Andi Kleen wrote:
> >
> > [snip]
> >
> > > Yes because you if modular works you don't need to build it in.
> > >
> > > Modular was working at some point on x86-64 for kdb and the original 2.6
> > > version of kgdb was nearly there too.
> >
> > FWIW, the only change the current version of kgdb makes that would
> > prevent it from being totally modular is the debugger_active check in
> > 
> 
> Can you post the patch and a description? 

It's maintained at SourceForge:

	http://sourceforge.net/projects/kgdb

Patches can be downloaded from:
	
	http://sourceforge.net/project/showfiles.php?group_id=5073

I suspect that you will likely want to add yourself to the
kgdb-bugreport mailing list.

	https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Mailing list is acting up; I've been having trouble posting due to
a mailserver problem; I contacted the SourceForge folks about it.

Andrew Morton has recently been taking snapshots and including them
in his mm series. It would be nice to get in "in order" and ready
for being merged up into the linux tree. When I applied the 2.6.13
patch I think I noticed some '#ifdef KGDB' code missing. I'd like 
to see the patch totally disabled by not configuring KGDB. The 
patch instructions are also a bit misleading, at least for 2.6.13;
I had to apply all of the patches in the series to avoid a lot a 
patch rejects. 

-piet

> 
> -Andi
-- 
---
piet@bluelane.com

[-- Attachment #2: Attached message - Re: mm patches - what's the heirarchy for patches on www.kernel.org web page? --]
[-- Type: message/rfc822, Size: 2943 bytes --]

From: Andrew Morton <akpm@osdl.org>
To: piet@bluelane.com
Subject: Re: mm patches - what's the heirarchy for patches on www.kernel.org web page?
Date: Thu, 20 Apr 2006 01:06:05 -0700
Message-ID: <20060420010605.5b0bc661.akpm@osdl.org>

Piet Delaney <piet@bluelane.com> wrote:
>
>  tried patching the latest stable kennel, 2.6.16.9 I thought, to
>  2.6.17.rc2 but got conflicts.

2.6.16.x is a branch, based on 2.6.16.

2.6.17-rcX is on the trunk.  The published diffs are against 2.6.16.

So you should have patched 2.6.16.


>  A few years ago Linus said he wanted to integrated the kgdb patch
>  but then stopped when he found our there were two patches. Now there
>  only seems to be one. Do you know why it's not being integrated into
>  the std linux kernel?

Nobody is doing the work to get the patches in order and merged up.  It'd
require a month or two moderately intense effort.

  parent reply	other threads:[~2006-05-31 22:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <446E0B4B.9070003@ru.mvista.com>
     [not found] ` <200605241240.05313.amitkale@linsyssoft.com>
     [not found]   ` <4474A1D0.30807@ru.mvista.com>
     [not found]     ` <200605251207.27699.amitkale@linsyssoft.com>
2006-05-31  4:45       ` Piet Delaney
2006-05-31  5:50         ` Andi Kleen
2006-05-31  6:46           ` Piet Delaney
2006-05-31  7:13             ` Andi Kleen
2006-05-31  8:39               ` Piet Delaney
2006-05-31  9:41                 ` Andi Kleen
2006-05-31 15:03               ` Tom Rini
2006-05-31 21:01                 ` Andi Kleen
2006-05-31 22:35                   ` Tom Rini
2006-05-31 22:59                     ` Andi Kleen
2006-05-31 22:52                   ` Piet Delaney [this message]
2006-05-31 23:03                     ` Piet Delaney

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=1149115945.26542.208.camel@piet2.bluelane.com \
    --to=piet@bluelane.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=amitkale@linsyssoft.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.org \
    --cc=vbarinov@ru.mvista.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

all inboxes | Powered by JetHome®