kdb
[Top] [All Lists]

Re: [PATCH 000/18] Introduction

To: "Jay Lan" <jlan@xxxxxxx>
Subject: Re: [PATCH 000/18] Introduction
From: "jidong xiao" <jidong.xiao@xxxxxxxxx>
Date: Mon, 14 Jul 2008 14:17:38 +0800
Cc: "Joe Korty" <joe.korty@xxxxxxxx>, KDB <kdb@xxxxxxxxxxx>, jim.houston@xxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=vpBg7e0m/Jup/BXc//EyfoQOHFRdPeqpW9Y7izvZlWI=; b=jMo5M1Ei2JTOY/iLRVOQKqOvhoZt2bWUkRyg/jEvrv3CrfYmFRb10FbUmA1qrTxjkN sIYjkuzJOGKgra5pSI+Mlyv5wZhhQIKNTfifsMYSg9AVcbKvcPm5OJreq71+plsCkzth Cm0HWQh/hP8/iOjl7rskwaALB1Sb5iy7n5u9w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IhqnFYzoFBvYK+BbfxguCKp01jxo3Pki4lxIMaKHhWuxLJIswiZ0o9lzPe5AtyugrP pJA4Bc1JQyu4P9y7xmmfl55hSCxAnN7Po0TGNulmhgzBmgBZ6Qp439L6LBf7H7YeGQwI zKfp3FWZqvO/Y9UNROprMh7ymLa50Gy6851bA=
In-reply-to: <4877D6C2.7040804@sgi.com>
References: <200807102053.m6AKrdVR031278@gamx.iccur.com> <4877D6C2.7040804@sgi.com>
Sender: kdb-bounce@xxxxxxxxxxx
On Sat, Jul 12, 2008 at 5:55 AM, Jay Lan <jlan@xxxxxxx> wrote:
> quilt@xxxxxxxxxxxxxxxx wrote:
>> This patch series ports kdb from 2.6.26-rc8 to -rc9,
>> defines some new kdb 'data structure display' commands,
>> and implements several little fixups and enhancements
>> that I've been using in KDB for a while.
>
> Hi Joe,
>
> Thanks a lot for your big patchset! I have integrated your
> patches (with exception of the kdump patch) plus the
> kdb-i386-boot-hang patch to kdb-v4.4-2.6.26-rc9-*.bz2.
>
> I think we can use a little bit more time on kdump-kdb
> integration. I have committed to making it happen from the
> KDB side since it sems not possible to get it done at the
> kernel upstreams.

Hi, Jay,
  Somehow I don't quite understand what your concern is, Dan's
patch(see the link I pasted in the previous email for details.) would
suffice for integrating kdump into kdb. I don't know why it was not
accepted. I took his patch and ported to i386, then I tested the kdump
command inside kdb, the result is okay, it works well in i386 and
x86_64, the kernel I was using includes a couple of releases between
2.6.16 and 2.6.18. If you need the patches against the latest kdb
release, I can submitted them to this maillist. In addition, I can
port it into ia64 and send you the patch later.

In the meanwhile,  I don't think the patch summitted by Joe, (I mean
the "kdump-kdb" patch) is really necessary.

Regards
Jason

>
> Regards,
>  - jay
>
>>
>> Regards,
>> Joe
>>
>> -----------
>> series file
>> -----------
>>
>> kdb-v4.4-2.6.26-rc8-common-1.bz2
>> kdb-v4.4-2.6.26-rc8-x86-1.bz2
>> #
>> kdb-vm-fl-insert
>> #
>> kdb-inatomic-usage
>> kdb-expand-kdb-cmderror
>> kdb-expand-dupl-cmd-error-msg
>> kdb-touch-nmi-watchdog
>> kdb-blade-8843-support
>> kdb-show-cpus-needing-nmi
>> kdb-ps-show-all
>> kdb-suppress-boottime-msgs
>> kdb-add-oops-breakpoint
>> #
>> kdb-cmd-memmap-discontigmem
>> kdb-add-numa-support-to-task-cmd
>> kdb-add-numa-support-to-vm-cmd
>> kdb-add-mempolicy-cmd
>> kdb-add-pgdat-cmd
>> kdb-add-kdump-cmd
>> ---------------------------
>> Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
>
>
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>